Bug 869576
Summary: | Cannot power-off after logout from gnome-shell session | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Milan Crha <mcrha> |
Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | gareth.k.jones, mark.harfouche, mschmidt, rstrode, tskd2 |
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: | 2014-02-05 12:41:46 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
Milan Crha
2012-10-24 10:12:52 UTC
I just wanted to say that this is still affecting users on Fedora 18 See thread http://forums.fedoraforum.org/showthread.php?p=1632052 (In reply to comment #0) > Interestingly, when I switch to a text console, login as root and do While you're there, please check out this: # to see the list of sessions loginctl # for the session ID number that was printed by the first command: loginctl session-status $SESSION_ID I cannot reproduce it now, I updated to latest Fedora 18 from updates right now. I still have this problem. mozc_server proccess does not terminate on logout, and it prevents shutdown without authentication. 1) boot up and login from gdm 2) logout 3) switch to VT2 and login then, always I can see my previous session remains. loginctl 2 500 tsukada seat0 4 42 gdm seat0 5 500 tsukada seat0 loginctl session-status 2 2 - tsukada (500) Since: Thu 2013-02-28 18:07:35 JST; 55min ago Leader: 1140 Seat: seat0; vc1 Display: :0 Service: gdm-password; type x11; class user State: closing CGroup: name=systemd:/user/tsukada/2 └─2197 /usr/libexec/mozc_server and if I kill the mozc_server process, this left-over session disappears. Fedora 18 kernel-3.7.9-205.fc18.x86_64 systemd-197-1.fc18.2.x86_64 mozc-1.6.1187.102-2.fc18.x86_64 ibus-mozc-1.6.1187.102-2.fc18.x86_64 ibus-gtk3-1.5.1-2.fc18.x86_64 ibus-1.5.1-2.fc18.x86_64 gnome-shell-3.6.3-2.fc18.x86_64 gnome-session-xsession-3.6.2-3.fc18.x86_64 gnome-session-3.6.2-3.fc18.x86_64 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. |