Bug 890827
Summary: | logind should ignore non-text and non-graphical sessions when checking whether shutdown shall be allowed | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | RudraB <bnrj.rudra> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | belegdol, covex, cpanceac, dennis, fat.lobyte9, gareth.k.jones, jcainfo, johannbg, lnykryn, manday, mark.harfouche, mcatanzaro+wrong-account-do-not-cc, metherid, mschmidt, msekleta, notting, oli, plautrba, pmatilai, systemd-maint, vpavlin |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-02-05 22:56:30 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
RudraB
2012-12-30 14:08:29 UTC
When this happens, what is the output of 'loginctl'? I will submit the output the next time this happens. To be sure that I submit correct loginctl, should I cancel the poweroff and take the output? I just got the error when I clicked "install updates and restart" As asked, here is the loginctl $ loginctl SESSION UID USER SEAT 2 1000 rudra seat0 4 0 root 5 42 gdm seat0 6 1000 rudra seat0 4 sessions listed. I just got the error when I clicked "install updates and restart" As asked, here is the loginctl $ loginctl SESSION UID USER SEAT 2 1000 rudra seat0 4 0 root 5 42 gdm seat0 6 1000 rudra seat0 4 sessions listed. (In reply to comment #4) > $ loginctl > SESSION UID USER SEAT ... > 4 0 root This could be a cron job belonging to root. Check it using: loginctl session-status 4 yes...crond is running! $ loginctl session-status 4 4 - root (0) Since: Thu, 2013-01-10 08:01:01 GMT; 42min ago Leader: 15419 Service: crond; type unspecified; class user State: closing CGroup: name=systemd:/user/root/4 └ 15431 /usr/sbin/anacron -s But I have not started any cron, and this problem was never shown in previous fedora releases. Hmm, we might want to ignore non-tty and non-graphical sessions for this check. *** Bug 840844 has been marked as a duplicate of this bug. *** Fixed upstream. http://cgit.freedesktop.org/systemd/systemd/commit/?id=1ca04b87979b2add53ebb8a7fdf13c34fb6c2743 systemd-197-1.fc18.2 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-197-1.fc18.2 Package systemd-197-1.fc18.2: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-197-1.fc18.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-1590/systemd-197-1.fc18.2 then log in and leave karma (feedback). *** Bug 906080 has been marked as a duplicate of this bug. *** *** Bug 907162 has been marked as a duplicate of this bug. *** Could this be the same bug? https://bugzilla.redhat.com/show_bug.cgi?id=869576 Looks like it. Lennart I got this today and it was the same issue, cron job running according to loginctl. However *I have already updated to systemd 197.* [michael@victory-road ~]$ loginctl list-sessions SESSION UID USER SEAT 3 0 root 5 0 root seat0 6 1000 michael seat0 3 sessions listed. [michael@victory-road ~]$ loginctl session-status 3 3 - root (0) Since: Wed 2013-02-13 21:01:01 CST; 13min ago Leader: 4519 Service: crond; type unspecified; class user State: closing CGroup: name=systemd:/user/root/3 └─4531 /usr/sbin/anacron -s (In reply to comment #15) > Lennart I got this today and it was the same issue, cron job running > according to loginctl. However *I have already updated to systemd 197.* But was it systemd-197-1.fc18.2 specifically? The last digit really really matters too. Oh I'm blind, sorry that is my fault for not reading properly. (I have 197-1.fc18.1.) *** Bug 911500 has been marked as a duplicate of this bug. *** Package initscripts-9.42.2-1.fc18, systemd-197-1.fc18.2: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initscripts-9.42.2-1.fc18 systemd-197-1.fc18.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-1590/initscripts-9.42.2-1.fc18,systemd-197-1.fc18.2 then log in and leave karma (feedback). initscripts-9.42.2-1.fc18, systemd-197-1.fc18.2 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. Reopening the bug, as this still happens to me, just the scenario is bit different. I am using IceWM and after I end up a session, I can not power off the machine for a few seconds from a GDM screen - I am still getting the dialog asking for a root password. After few attempts it suddenly powers off OK. It looks to me, like there is some kind of timeout or polling before the shutdown works. So far I was not able to get the loginctl output within this period. 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. |