Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1266294
| Summary: | not able to relogin after a first logout | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | nmreis | ||||||
| Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 23 | CC: | awilliam, fmuellner, otaylor, scorpy_sk | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-12-20 14:44:50 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: | |||||||||
| Attachments: |
|
||||||||
Can we please get the journalctl output too? Thanks. (In reply to nmreis from comment #0) > The only way to login again is by rebooting the machine. Does "loginctl terminate-user <username>" (as root) work around the issue without a reboot? Hi Florian. It did work, as a work around. I'm also attaching all the logs a think might be usefull here. Created attachment 1077988 [details]
other usefull logs from journal/dmesg
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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 this bug is closed as described in the policy above. 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. |
Created attachment 1076832 [details] dmesg output Description of problem: updating mutter solved the first problem reported on bug: 1264904, but now I have a new one: After the first login on any user (fedora with 2 different users), if I logout and try to login again, the process fails and basically I get stuck on login. The only way to login again is by rebooting the machine. Version-Release number of selected component (if applicable): Fedora 23. How reproducible: always. Steps to Reproduce: 1. Login on gnome3 after boot 2. Logout 3. Try to login again Actual results: Not able to login anymore. dmesg says systemd-logind is tainted and a stacktrace is printed. Expected results: Be able to login/logout over and over without rebooting. Additional info: After boot and I'm not sure if it is related gnome-shell also crashes a lot. Take a look on the attached file with the actual dmesg output after a clean reboot.