Hide Forgot
Fedora 24 with GDM as the display manager: - Boot to the login screen - User A logs in with standard GNOME - User A locks their screen and someone presses the "Log in as another user" button - User B logs in - Now user A contacts the machine remotely and kills off their gnome-session process. Suddenly user B, who was happily using the computer and has no idea what's going on, is looking at the login screen. I believe what's happening is that when user A's session ends, X is VT switching on termination back to the VT that user A was logged in on, and then systemd-logind is VT switching back to the login screen. On the other hand, this also happens if user A selects "GNOME on Wayland" at login so it's not entirely X's fault. This is inconvenient both because it permits a non-root user to prank another user, and because in a lab environment where we might want to terminate idle sessions we risk annoying active users by sending them to the login screen. I don't know if it can be fixed, but (a) can we make X not do a VT switch if it wasn't active when it terminated, and/or (b) can we make systemd-logind VT switch to the most recently active user instead of to the login screen, in the cases when it wasn't the most recently active user who logged out? Systemd is definitely involved because it still happens if I kill -9 the X server so that it doesn't have chance to do the VT switch on exit. Tested on: systemd-229-16.fc24.x86_64 gdm-3.20.1-3.fc24.x86_64 xorg-x11-server-Xorg-1.18.4-5.fc24.x86_64
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still observed systemd-233-6.fc26.x86_64 gdm-3.24.2-1.fc26.x86_64 xorg-x11-server-Xorg-1.19.3-4.fc26.x86_64
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.