Red Hat Bugzilla – Bug 807177
Gnome session goes unusable after cancelling root's password request on reboot
Last modified: 2016-05-05 00:40:29 EDT
Description of problem:
Gnome session goes in wallpaper-only-state after cancelling root's password request on reboot or shutdown when more than 1 user is logged on the system in gnome or fallback.
Version-Release number of selected component (if applicable):
Fedora 17 Beta RC1
Steps to Reproduce:
1. Log into system with more than 1 user (use 'switch user' button when screen locked for example)
2. Try to perform shutdown or reboot in one's user account (not in login screen), you are prompted for root password
3. Click cancel button
You have to click the cancel button multiple times and after that your session remains in unusable state (wallpaper only).
You can go on with work in your session.
Applied in gnome-shell even in fallback.
gnome-session-3.4.0-2.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-session-3.4.0-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Installed Fedora 17 Beta RC4 and updated gnome-session to 3.4.0-2 according to instructions and tried to reproduce this bug using the same steps.
Screen does not lock anymore, but actual result is that user is kicked from session (to gdm).
gnome-session-3.4.0-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
I still experience problems when two or more users are logged in gnome and I try to shutdown/restart system and then cancel root's password request.
Tested on Fedora final TC2, gnome-session-3.4.1-2.fc17.x86_64. Both users logged in were kicked with no warning/message.
Problem persists in Fedora 17 final RC3. Log in a user, select switch users, log in second user, reboot/poweroff and then cancel on password request leads to abrupt termination of user session. Applies on GNOME "new" and fallback.
I experimented a similar problem. In my case, only 1 user was logged in and that user's password was required. Cacelling the authentication led to logout (or it might have been termination of user session as Filip Skola says above). I don't remember whether I clicked cancel button or pressed ESC key. Since then, gdm has always been in fallback mode.
I haven't tried to reproduce this issue because the password isn't required for reboot or shutdown anymore.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora
'version' of '17'.
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 prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.