Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: When trying to reboot or shutdown I was shown a message that there are other sessions running in the system and I need to input a password to perform a system shutdown. My session was the only session but after executing 'systemd-loginctl' I could see my session and a root session. It happened once I got my session, a root session and a gdm user session. Where did those sessions came from when I'm the only user and just turned the laptop on few minutes ago? I've 3 laptops in the house and this behaviour is happening randomly in all systems. The ssh service is down and the firewall is turned on with default configurations. I'm under a protected MAC address filtered home network with a wi-fi encrypted WPA connection. It must be something running in the system that is causing this behaviour and it should not happen. Version-Release number of selected component (if applicable): It's happening with a fresh install of fedora 18. How reproducible: Randomly, sometimes the root session is there sometimes I just lets me turn off the laptop. Steps to Reproduce: 1. Logon 2. Logoff Actual results: Sometimes I need to type my password to shutdown. Expected results: When there's only one session it should let the user shutdown. What are those ghosts sessions? Additional info: This incident already drained my laptop battery. I was surprised it was not turning on. Later I found what happened, I did the shut down operation and the system popup a message info telling the system will turn off in 60 seconds. That time I left the laptop and when out. When I was out, 60 seconds after the system popup to insert my password and didn't shut down and drained the laptop battery until it naturaly turns off.
[myuser@mylaptop ~]$ systemd-loginctl SESSION UID USER SEAT 5 1000 myuser seat0 6 0 root 2 sessions listed. [myuser@mylaptop ~]$ sudo systemd-loginctl kill-session 6 [sudo] password for myuser: Failed to issue method call: No such process [myuser@mylaptop ~]$ systemd-loginctl SESSION UID USER SEAT 5 1000 myuser seat0 1 sessions listed.
I got what root session is up to: systemd-loginctl user-status root root (0) Since: Qui 2013-01-24 20:01:02 WET; 17min ago State: active Sessions: 3 CGroup: name=systemd:/user/root └─3 └─1920 /usr/sbin/anacron -s is this the cause? I can't shut down because of an anacron task?
Possibly related to bug #913299
It's been a long this issue does not happen. Maybe it's gone in some update.
I'm still seeing it on Fedora 19.
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.
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.