Manjaro shutting down at night after most recent updates

[seasoned_geek]

Have two machines running same Manjaro distro. Here is one.

Things were fine until last round of system updates. Now, despite

both machines completely shut down at night. Log my process out, crashing my editors and browsers. I even have BOINC running in background on both machines so they are never “idle” for very long.

Where oh where has the newest hidden power setting been placed?

I’m not sitting in my office at night, but it seems like someone created a shiny new “security” setting. If there is no user input from keyboard/mouse for N-hours it just kills off the login.

I’m a developer. I don’t log out. I leave browsers, editors, and terminals open with notes on where to start when I come back in. It even kills off Clementine (music player) that is in second workspace.

Not a full shutdown because my network drives are still connected when I log back in.

Please, somebody tell me where this new setting is hidden so I can fix it.

Thanks,

[mithrial]

@seasoned_geek

I’m a developer. I don’t log out. I leave browsers, editors, and terminals open with notes on where to start when I come back in. It even kills off Clementine (music player) that is in second workspace.

This is a very luxurious attitude. At least put your device to sleep (suspend) if not hibernation.

It might be a setting of your lockscreen. Without hardware information or a log (journal), there’s nothing to go on from here.

[seasoned_geek]

@mithrial

This is a very luxurious attitude. At least put your device to sleep (suspend) if not hibernation.

Not luxurious. I run BOINC when not using the machine for development to help cure cancer, HIV, COVID-19, and other diseases. Putting my device to sleep would mean more people die than necessary. I don’t know where you live, but in America many of us with good machines participate in BOINC or other research projects donating the “idle” time to make the world a better place.

It is most definitely not a lockscreen. The lockscreen has been busted on both Manjaro Cinnamon and XFCE for quite some time.

Only workaround is to completely disable.

@mithrial

Without hardware information or a log (journal), there’s nothing to go on from here.

You need to specify exactly what file or information you require. Especially which “(journal)”

System:
  Kernel: 5.15.94-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1 Desktop: Cinnamon
    v: 5.6.7 tk: GTK v: 3.24.36 dm: LightDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: HP product: HP Z2 SFF G4 Workstation v: N/A serial: <superuser required>
    Chassis: type: 3 serial: <superuser required>
  Mobo: HP model: 8456 v: KBC Version 07.D1.00 serial: <superuser required> UEFI: HP
    v: Q50 Ver. 01.08.03 date: 11/03/2022
CPU:
  Info: 6-core model: Intel Core i7-8700 bits: 64 type: MT MCP arch: Coffee Lake rev: A cache:
    L1: 384 KiB L2: 1.5 MiB L3: 12 MiB
  Speed (MHz): avg: 895 high: 901 min/max: 800/4600 cores: 1: 900 2: 900 3: 900 4: 881 5: 869
    6: 901 7: 900 8: 900 9: 900 10: 900 11: 900 12: 900 bogomips: 76831
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GF119 [NVS 310] vendor: Hewlett-Packard driver: nvidia v: 390.157 arch: Fermi
    pcie: speed: 5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:107d
  Device-2: ARC Camera type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-11.2:6
    chip-ID: 05a3:9331
  Display: x11 server: X.Org v: 21.1.7 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 81
  Monitor-1: DP-0 pos: right res: 1920x1080 dpi: 82 diag: 686mm (27.01")
  Monitor-2: DP-1 pos: primary,left res: 1920x1080 dpi: 82 diag: 686mm (27.01")
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
    bus-ID: 1-11.2:6 chip-ID: 05a3:9331 bus-ID: 00:1f.3 chip-ID: 8086:a348
  Device-2: NVIDIA GF119 HDMI Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie:
    speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e08
  Device-3: ARC Camera type: USB driver: snd-usb-audio,uvcvideo
  Sound API: ALSA v: k5.15.94-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.22 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.65 running: yes
Network:
  Device-1: Intel Ethernet I219-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15bb
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 10.92 TiB used: 3.04 TiB (27.8%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN770 1TB size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 30.9 C
  ID-2: /dev/sda vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB speed: 6.0 Gb/s
    serial: <filter>
  ID-3: /dev/sdb type: USB vendor: Seagate model: Backup+ Hub BK size: 5.46 TiB serial: <filter>
  ID-4: /dev/sdc type: USB vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB
    serial: <filter>
Partition:
  ID-1: / size: 915.53 GiB used: 25.18 GiB (2.8%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 29.0 C pch: 51.0 C mobo: N/A gpu: nvidia temp: 50 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 1246 pm: pacman pkgs: 1242 pm: snap pkgs: 4
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https: //coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    2: http: //mirror.fcix.net/manjaro/stable/$repo/$arch
    3: https: //mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    4: http: //ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    5: https: //repo.skni.umcs.pl/manjaro/stable/$repo/$arch
    6: https: //mirror.ufam.edu.br/manjaro/stable/$repo/$arch
    7: https: //ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    8: https: //mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
Info:
  Processes: 355 Uptime: 4d 20h 44m Memory: 31.08 GiB used: 30.42 GiB (97.9%) Init: systemd v: 252
  default: graphical Compilers: gcc: 12.2.1 clang: 15.0.7 Client: Cinnamon v: 5.6.7 inxi: 3.3.25

[bogdancovaciu]

Random questions:

• is your office closed and nobody else has access to it over night?
• does the building where your office is located have a Save Energy feature ? (as many towns in the world use that) so the main power is off at certain hours over night, or if are cubicles they have occupancy sensors that turn off the power when there is nobody there …

[seasoned_geek]

Sorry,

I thought I replied to you a long time ago.

I live on a farm in the middle of nowhere. I have one neighbor a 1/4 mile away and the next is over a mile. I built the building I use for my office over 20 years ago. It doesn’t have any energy saving power shut-off stuff installed because it didn’t exist then. No, I don’t have people randomly coming into my office building that I lock at night. I’m the only one who works here.

I did manage to fix this. I had to use Dconf Editor and some other forum pointed me to Gnome power settings that weren’t available from the UI. I forget which ones. Once I changed them the shutdown problem went away.

Will put a task on my todo list to see if I can find which values. They weren’t obvious.