The user cannot hibernate the system if another user has logged in and out of the system. Reproducible: Always Steps to Reproduce: 1. Need two users (user1 & user2) who can log in to the system. 2. Login to the system as user2. 3. Log out of the system. 4. Log in as user1 5. Check the output of the command 'who' from a terminal to ensure that the system does report only the user1. 6. Hibernate the system. 7. The lock screen will be displayed and the system will not hibernate. Actual Results: Instead of hibernating, the system will display the lock screen and stay there. Expected Results: When step #6 is executed, the system should hibernate. Even though who command in step #5 list the user2, ps -fu user2 will show that the following command is being run from user2's id: /usr/bin/gpg-agent -s --daemon --write-env-file /run/user/1001/.gpg-agent-info If the screen is unlocked, one can see the window titled "Authentication is required for hibernating the system while other users are logged in. - PolicyKit1-KDE" requesting for the root password. I suspect the prompt for the root password has come as /usr/bin/gpg-agent is active from user2 id. As far as I know, all the process that were started by the graphical login should be terminated when the user logs out of KDE. Not sure the reason why the /usr/bin/gpg-agent process is still running. In this case the user1 cannot hibernate the system without root password. Bug 328336 (https://bugs.kde.org/show_bug.cgi?id=328336) is raised to address the sequence in which the password prompt and lock screen are shown.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
No response; assuming it was fixed since then.