Hide Forgot
Description of problem: user is logged out of gui after switching from a root gui session after trying to shutdown and cancelling the shutdown Version-Release number of selected component (if applicable): RHEL 6.7 How reproducible: Verified in house on a 6.6 system Steps to Reproduce: - Have root log into the gnome desktop - Switch to another user without elevated privileges - Attempt to shutdown from the menu - The user will be prompted for the root password - Click cancel and the user will be logged out and immediately be switch to the root desktop <<<<<< (The problem is here) ( I believe that I should have to authenticate to return to root's desktop session) Actual results: - user is logged out and switched back to the root session without authentication prompt Expected results: - I expect that the correct behavior is for the user to be put back on his/her own desktop and not root Additional info: Spoke with Ray Strode about this directly, he verified it is an issue
To be clear, we don't lock the screen for the root user in RHEL 6 (or earlier RHELs). That's one of the reasons we post a warning dialog when a user logs in as root. The bug here is that we log the user out when they shutdown, before we ask for the polkit password. If they cancel the polkit password, we've already logged the user out so we can't perform the cancel. We should get the polkit credentials first before doing the logout. I don't think we should change the behavior of root locking in rhel 6 at this point. That behavior has existed since before RHEL 2.1. See https://wiki.gnome.org/Projects/GnomeScreensaver/FrequentlyAskedQuestions#Why_doesn.27t_my_screen_lock_when_I.27m_logged_in_as_root.3F We did fix it for rhel 7, though.
I've done a build now with the changes mentioned in comment 2.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0788.html