Yesterday I migrated my Fedora 37 to Fedora 38 in three Apple Mac mini Intel and one AppleMacPro "trash can".
The Apple Mac Minis are working very well. I assume is because they do not have any GUI installed...
For some reason GDM in the Apple Mac Pro is suspending the machine after few minutes up. I found few discussions about related topics, dated back to 5 years ago. I have been trying many different settings but with no satisfactory results.
Since the machine is powering off/suspending regularly, I have not too much time to collect information or set anything, before it goes down again...
This is the status:
$ uname -a Linux HG000009 6.2.11-300.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 13 20:27:09 UTC 2023 x86_64 GNU/Linux
$ sudo -u gdm dbus-run-session gsettings list-recursively org.gnome.settings-daemon.plugins.power org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power power-button-action 'nothing' org.gnome.settings-daemon.plugins.power power-saver-profile-on-low-battery false org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout -1 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout -1 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing'
$ sudo dbus-run-session gsettings list-recursively org.gnome.settings-daemon.plugins.power org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power power-saver-profile-on-low-battery true org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 900 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 900 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'
Those are the last entries in /var/log/message before system shutdown
Apr 19 10:07:21 HG000009 systemd-logind[2593]: Delay lock is active (UID 1000/afberendsen, PID 5625/gnome-shell) but inhibitor timeout is reached. Apr 19 10:07:21 HG000009 system[1]: Reached target sleep.target - Sleep. Apr 19 10:07:21 HG000009 system[1]: Starting systemd-suspend.service - System Suspend... Apr 19 10:07:21 HG000009 systemd-sleep[407534]: Entering sleep state 'suspend'... Apr 19 10:07:21 HG000009 kernel: PM: suspend entry (s2idle)
This is the contents of /etc/system/login.conf (commented lines out)
[Login] HandleSuspendKey=ignore HandleSuspendKeyLongPress=ignore HandleLidSwitch=ignore HandleLidSwitchExternalPower=ignore
$ inxi CPU: 6-core Intel Xeon E5-1650 v2 (-MT MCP-) speed/min/max: 1808/1200/3900 MHz Kernel: 6.2.11-300.fc38.x86_64 x86_64 Up: 8m Mem: 36457.6/64257.8 MiB (56.7%)
$ sudo dmidecode -t system # dmidecode 3.4 Getting SMBIOS data from sysfs. SMBIOS 2.4 present. Handle 0x0010, DMI type 1, 27 bytes System Information Manufacturer: Apple Inc. Product Name: MacPro6,1 Version: 1.0 Serial Number: ********* UUID: *************** Wake-up Type: Power Switch SKU Number: Not Specified Family: MacPro Handle 0x003C, DMI type 32, 20 bytes System Boot Information Status: No errors detected Handle 0x003E, DMI type 12, 5 bytes System Configuration Options
I found this page, which I am trying to implement the recommended solution: https://bbs.archlinux.org/viewtopic.php?id=196220. Let's see the outcome of it.
/etc/dconf/local.d/01-power
sleep-inactive-ac-type='nothing' sleep-inactive-battery-type='nothing' sleep-inactive-ac-timeout=99999 sleep-inactive-battery-timeout=99999
After 26 minutes, things are working now. Not sure if it was caused by the repetitive reboots while I was implementing the changes OR if I must wait for 99999 minutes to see the outcome.
This issue tracker is for policy decisions of the Workstation Working Group, not for bug reports.
That said, your laptop was configured to sleep after 15 minutes when on battery power. Now you've configured it to sleep after 28 hours (99999 seconds). You might want to just turn off sleep in system settings (Power panel) if you don't want it to go to sleep.
Metadata Update from @catanzaro: - Issue close_status updated to: Won't fix - Issue status updated to: Closed (was: Open)
My point is: it was working on fedora 37. After upgrading to Fedora 38 this problem began. I made all the necessary changes in the Gnome GUI interface without any success.
Do you have gdm still running? If so, it will now sleep after 15 minutes even when plugged in (previously this would happen only after 20 minutes and when on battery power). But it would be weird for gdm to be running while you're logged into GNOME.
Umm...Interesting comment...I have this machine installed on Fedora 35, and have been upgrading it since then. Now is at 38 and the problem popped.
I am logged in right now (using VNC).
$ ps aux|grep -i gdm root 4625 0.0 0.0 525624 7808 ? Ssl 10:20 0:00 /usr/sbin/gdm root 4665 0.0 0.0 459724 10240 ? Sl 10:20 0:00 gdm-session-worker [pam/gdm-launch-environment] gdm 4710 0.0 0.0 19812 10112 ? Ss 10:20 0:01 /usr/lib/system/system --user gdm 4731 0.0 0.0 25636 4208 ? S 10:20 0:00 (sd-pam) gdm 4855 0.0 0.0 448296 5248 tty1 Ssl+ 10:20 0:00 /usr/libexec/gdm-wayland-session dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm 4858 0.0 0.0 9044 4096 ? Ss 10:20 0:00 /usr/bin/dbus-broker-launch --scope user gdm 4862 0.0 0.0 4740 2432 ? S 10:20 0:00 dbus-broker --log 4 --controller 10 --machine-id cdebfb651fcc4ea68be99296397de688 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000 gdm 4865 0.0 0.0 5000 2176 tty1 S+ 10:20 0:00 dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm 4866 0.0 0.0 8456 4352 tty1 S+ 10:20 0:00 dbus-daemon --nofork --print-address 4 --session gdm 4867 0.0 0.0 773284 12288 tty1 Sl+ 10:20 0:00 /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart gdm 4877 0.0 0.2 4930084 139824 tty1 Sl+ 10:20 0:13 /usr/bin/gnome-shell gdm 5067 0.0 0.0 380668 6784 tty1 Sl+ 10:20 0:00 /usr/libexec/at-spi-bus-launcher gdm 5073 0.0 0.0 7724 4352 tty1 S+ 10:20 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 12 --address=unix:path=/run/user/42/at-spi/bus gdm 5116 0.0 0.0 565220 25568 tty1 Sl+ 10:20 0:00 /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/42/.mutter-Xwaylandauth.ITZL31 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients gdm 5270 0.0 0.0 521920 5120 tty1 Sl+ 10:20 0:00 /usr/libexec/xdg-permission-store gdm 5288 0.0 0.0 259524 10880 ? S<sl 10:20 0:00 /usr/bin/pipewire gdm 5289 0.0 0.0 551992 22784 ? S<sl 10:20 0:07 /usr/bin/wireplumber gdm 5290 0.0 0.0 241944 8576 ? S<sl 10:20 0:00 /usr/bin/pipewire-pulse gdm 5308 0.0 0.0 3166708 21848 tty1 Sl+ 10:20 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications gdm 5334 0.0 0.0 233436 6400 tty1 Sl+ 10:20 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session gdm 5343 0.0 0.0 754572 9984 tty1 Sl+ 10:20 0:03 /usr/libexec/gsd-sharing gdm 5349 0.0 0.0 628932 12976 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-wacom gdm 5351 0.0 0.0 629968 14528 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-color gdm 5360 0.0 0.0 628196 14400 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-keyboard gdm 5361 0.0 0.0 541928 12416 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-print-notifications gdm 5365 0.0 0.0 743748 6016 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-rfkill gdm 5368 0.0 0.0 684024 12928 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-smartcard gdm 5378 0.0 0.0 613000 9600 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-datetime gdm 5383 0.0 0.0 773972 16124 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-media-keys gdm 5395 0.0 0.0 522228 5632 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-screensaver-proxy gdm 5403 0.0 0.0 604652 8704 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-sound gdm 5404 0.0 0.0 596552 6016 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-a11y-settings gdm 5416 0.0 0.0 672804 7168 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-housekeeping gdm 5418 0.0 0.0 777304 15028 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-power gdm 5442 0.0 0.0 229044 5248 tty1 Sl+ 10:20 0:00 /usr/libexec/dconf-service gdm 5453 0.0 0.0 637724 13952 tty1 Sl+ 10:20 0:00 /usr/libexec/gsd-printer gdm 5501 0.0 0.0 526208 7040 tty1 Sl+ 10:20 0:00 /usr/libexec/gvfsd gdm 5843 0.0 0.0 3158508 20316 tty1 Sl+ 10:20 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver gdm 5849 0.0 0.0 1179924 27316 tty1 Sl+ 10:20 0:00 /usr/libexec/mutter-x11-frames gdm 5861 0.0 0.0 602400 9588 tty1 Sl 10:20 0:00 ibus-daemon --panel disable -r --xim gdm 5890 0.0 0.0 523092 6016 tty1 Sl 10:20 0:00 /usr/libexec/ibus-dconf gdm 5895 0.0 0.0 523024 6528 tty1 Sl+ 10:20 0:00 /usr/libexec/ibus-portal gdm 5940 0.0 0.0 449400 6400 tty1 Sl 10:20 0:00 /usr/libexec/ibus-engine-simple gdm 13040 0.0 0.0 538640 48676 tty1 Sl 10:21 0:01 /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --ibus afberen+ 1047488 0.0 0.0 222544 2432 pts/11 S+ 15:22 0:00 grep --color=auto -i gdm
Well there's the problem. If gdm is running it's going to auto-suspend according to its own settings, not according to your user account settings. I suggest a bug report, perhaps to gdm for starters, although that may not be the final component it winds up with.
Explanation and solution here
https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801
Login to comment on this ticket.