| Summary: | Gnome-shell 2 concurrent user logged in cause gdm to not respond after resume | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jon Dufresne <jon.dufresne> | ||||||||
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | jmccann, maxamillion, mcepl, otaylor, rstrode, samkraju, walters, xgl-maint | ||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-04-06 14:22:47 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Jon Dufresne
2011-03-27 15:15:25 UTC
Unlikely to be a GNOME Shell bug. Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 488621 [details]
Xorg log
Created attachment 488622 [details]
dmesg output
Created attachment 488623 [details]
System messages
I have attached the requested information. Please let me know if there is any other information that I can provide. After this has happened a few more times, it appears the freezing only occurs for the second user logged in simultaneously and never for the first user logged in. Still not sure how to consistently reproduce. Can you ssh in after this happen ? If so does changing init level to 3 and then back to 5 (ie shutting down X server) give you back a working X (you will loose current session of course). To me it's looks like a gnome bug (look for Mar 29 09:16:12 in message to see error about thread in glib/gdm/gnome password greeter). > Can you ssh in after this happen ? Yes. I can even Alt + FX to drop to a terminal. I can also Ctrl + Alt + Backspace to restart X. After the restart the session appears to be working fine. > If so does changing init level to 3 and then back to 5 (ie shutting down X server) give you back a working X (you will loose current session of course). I haven't tried this, but I imagine it would work since the Ctrl + Alt + Backspace works. Definitly not a driver bug, looks like gnome/gdm/screensaver is confuse having multiple user and don't know which should be unlocked on resume This bug still occurs daily for me. Assigning to correct people so they actually notice the bug I now have more reason to believe that Gnome is getting confused about multiple concurrent users. When this bug is going to happen, if I choose "Log out" rather than "Switch user" then Gnome goes to a virtual terminal that is not displaying X, and I just see a blinking cursor. Hitting ctrl + alt + FX until I get the right combo eventually gets me back at the expected desktop. This now occurs on a daily basis. My system is up to date and I have rebooted since a recent update. Every morning that I approach my computer, if I switch users and then log in, GNOME shell will freeze when clicking "Activities". I would be happy to provide additional information if it would help solve this issue. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This issue has not occurred in GNOME 3.2 and Fedora 16. |