Fedora Account System
Red Hat Associate
Red Hat Customer
Hi Everyone. I just system-upgraded a machine from F37 to F38 following https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ . I'm in the post-upgrade cleanup tasks, like removing old packages, removing old kernels and cleaning up old symlinks. At the step "Clean-up old symlinks" GDM put the machine to sleep. It happened at exactly 15 minutes after SSH'ing into the machine. Here's what the terminal looks like: <BEGIN TERM MSGS> skylake:~$ sudo symlinks -r / | grep dangling dangling: /etc/fonts/conf.d/65-0-thai-scalable-waree.conf.rpmsave -> ../../../usr/share/fontconfig/conf.avail/65-0-thai-scalable-waree.conf ... dangling: /usr/bin/xelatex-unsafe -> /usr/share/texlive/texmf-dist/scripts/texlive-extra/xelatex-unsafe.sh dangling: /usr/bin/xetex-unsafe -> /usr/share/texlive/texmf-dist/scripts/texlive-extra/xetex-unsafe.sh skylake:~$ Broadcast message from gdm@skylake on tty1 (Sat 2023-04-22 12:26:40 EDT): The system will suspend now! </END TERM MSGS> And the terminal stops accepting commands. I cannot log back into the machine: <BEGIN TERM MSGS> coffee:~$ ssh skylake ssh: connect to host skylake port 22: No route to host </END TERM MSGS> The machine is headless. And worse, I need to drive across town to put a monitor and keyboard on it. This is new behavior. And in my case, I can say it is unwanted behavior.
This bug may be related, but it looks like it did not get attention: * Systemd service should inhibit suspend while remote users are logged in via ssh, https://bugzilla.redhat.com/show_bug.cgi?id=837109
This looks like a problem with https://src.fedoraproject.org/rpms/gnome-settings-daemon/c/c8f9665aca0617a921ec308a0f1d2741d92dc41d?branch=rawhide . Thanks to u/EatMeerkats on Reddit for finding the cause. https://www.reddit.com/r/Fedora/comments/12vfnt8/f38_suspends_with_active_ssh_connections/ .
Reassign to gnome-settings-daemon team. It does not appear to be a GDM problem.
OK, we are another year later, and the ssh session is still not preventing the workstation system to go to sleep while user is logged in and everybody needs to manually disable this as described here https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801 I am happy we have a lenovo power certification, but it drives me crazy every time Fedora suspends with "The system will suspend now!" when I work there over ssh.
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.