Bug 911500

Summary: can not shutdown as user even nobody is logged in
Product: [Fedora] Fedora Reporter: Adam Pribyl <covex>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, systemd-maint, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-15 09:43:23 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 Adam Pribyl 2013-02-15 08:26:27 UTC
Description of problem:
For reason unknown to me, I could not shutdown my machine once while there was nobody logged in anymore. Logging onto tty as root, systemd-loginctl shows active session for a user, while there was no user really active anymore.

# systemd-loginctl
   SESSION        UID USER             SEAT
         2        500 covex            seat0
       531         42 gdm              seat0
       534          0 root             seat0

3 sessions listed.
[root@mejvis ~]# ps axu | grep covex
root       546  0.0  0.0 109176   844 tty2     S+   08:57   0:00 grep --color=auto covex

There were no processes visible for user that has seat active according to systemd.

Version-Release number of selected component (if applicable):
systemd-197-1.fc18.1.x86_64

How reproducible:
Rarely.

Steps to Reproduce:
Unknown so far. 

Note: Using icewm.

Comment 1 Michal Schmidt 2013-02-15 09:43:23 UTC
Likely a duplicate of 890827.
Please reopen if it happens again with systemd >= systemd-197-1.fc18.2.

*** This bug has been marked as a duplicate of bug 890827 ***

Comment 2 Michal Schmidt 2013-02-15 09:44:34 UTC
And if it happens, check "loginctl session-status $ID" for IDs of any suspicious sessions.