Bug 913299

Summary: System sometimes refuses to shutdown, falsely claiming other users are logged in.
Product: [Fedora] Fedora Reporter: Chris Rankin <rankincj>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 18CC: garrett.mitchener, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:21:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chris Rankin 2013-02-20 21:48:41 UTC
Description of problem:
Fedora 18 sometimes refuses to shutdown when asked, falsely claiming that other users are still logged in. It then demands that the user enter the root password. Users who don't know the root password then say "Fuck this" and turn the power off instead.


Version-Release number of selected component (if applicable):
gdm-3.6.2-5.fc18.i686


How reproducible:
Sometimes, ever since Fedora 18 was installed.


Steps to Reproduce:
1. Power on the PC, and wait for the login menu.
1. One user ONLY then logs into GNOME3.
2. The single user "does stuff".
3. Finally, this single user selects "Power Off" from the status menu.
  
Actual results:
Sometimes, the system claims that another user is somehow still logged in. At this point, it demands the root password before proceeding.

Expected results:
When the ONLY logged in user selects the "Power Off" option, the PC should ALWAYS turn itself off.

Additional info:
Typing "users" from the command line in these cases reveals that there is an extra "(unknown)" user logged in. Could something be corrupting the /var/run/utmp file?

On one occasion, I selected "Log Out" instead of "Power Off" and then tried to Power Off from the greeter screen instead. The "fake user is still logged in" problem still occurred. Logging into a console as root revealed that the "gdm-simple-slave" process held an open file descriptor for /var/run/utmp.

Comment 1 Garrett Mitchener 2013-04-28 22:04:06 UTC
Possibly related to bug #903389

Comment 2 Fedora End Of Life 2013-12-21 11:34:27 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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.

Comment 3 Fedora End Of Life 2014-02-05 19:21:11 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.