Bug 2071394
| Summary: | Connecting/disconnecting an external monitor or VM resizing switches GNOME to the login screen | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | grumpey0 | ||||
| Component: | gnome-shell | Assignee: | Florian Müllner <fmuellner> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 37 | CC: | adscvr, bcotton, emailtoflorian, fmuellner, fzatlouk, gnome-sig, jadahl, james, klember, kparal, ludvigng, otaylor, philip.wyett, robatino, rstrode, simone.tolotti, vondruch, vtq-gnome | ||||
| Target Milestone: | --- | Keywords: | CommonBugs, Reopened | ||||
| Target Release: | --- | Flags: | bcotton:
fedora_prioritized_bug-
|
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | https://ask.fedoraproject.org/t/common-issues/21076 RejectedBlocker AcceptedFreezeException | ||||||
| Fixed In Version: | gdm-43.0-1.fc37 gdm-43.0-1.fc38 gnome-shell-43.0-1.fc37 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-09-22 01:46: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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1953786 | ||||||
| Attachments: |
|
||||||
|
Description
grumpey0
2022-04-03 15:39:13 UTC
Also reported at: https://ask.fedoraproject.org/t/gnome-goes-to-the-login-screen-after-plugging-in-out-external-monitor-for-the-first-time-since-boot/21063?u=grumpey Proposed as a Blocker for 36-final by Fedora user lruzicka using the blocker tracking app because: I am proposing this bug because it violates the *Dual monitor setup* release criterion. https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Dual_monitor_setup I can reproduce this issue easily on my Thinkpad T480s. It happens the first time I connect an external monitor while being already logged in, or the first time I disconnect an external monitor (if I booted with it already connected). In both cases, I'm switched to gdm. However, please note that I haven't seen any data loss. My session is still running, it hasn't crashed. I just need to log in again, in order to be switched to my existing session. So while it is annoying and confusing, it doesn't seem to cause any data loss. Discussed during the 2022-04-04 blocker review meeting: [1] The decision to classify this bug as an RejectedBlocker and AcceptedFreezeException was made: "This is an ugly bug, but we don’t think it violates the blocker criteria as stated and agree that the impact it has is minimal. We do grant an FE though as it would be nice to have if a fix were available." [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-04-04/f36-blocker-review.2022-04-04-16.00.log.html I can reproduce this issue when putting my Thinkpad T450s into its docking station - thrown back to GDM to re-login, but no data loss. Gnome session is not crashing. This also affects virtual machines - virt-manager, Boxes (both tested by me) and VirtualBox [1]. When you resize the VM window, and you have VM autoresize enabled, it switches you to gdm during the resize process. After repeated login, you session is still running, with the desktop size changed. In Boxes in particular, this also affects the Live image - it boots into desktop due to autologin, but then resizes the screen which switches you back to gdm. Manual resolution change in the VM seems to work as expected, no session switching. [1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/2J62APXU2GSC6HN3DQO2MIKVUPR4235D/ This also occurs with both monitors on after screen blanking is activated after a reboot or after initial boot. Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5294 I couldn't reproduce the screen blanking case, even with multiple monitors. For me, I see the lock screen (even after a fresh reboot). I don't know if it is related to this bug, but when I start F36 with a second monitor connected, GDM access is blocked, meaning that I cannot interact with neither the mouse nor the keyboard to select the user and enter the password. If I unplug and plug the monitor back in, GDM will work properly again. Simone, that's not the case for me, I can log in just fine using two monitors. However, try if your input starts working after pressing Esc. There are weird input issues lately in GNOME, perhaps a bit related to bug 2063156. Proposing as a prioritized bug. This has multiple consequences and it's very visible to anyone using multiple monitors or docking stations. The screen blanking case was also reported multiple times. it's a bit of a guess, but I think this build may fix the problem. Would someone mind trying? https://koji.fedoraproject.org/koji/taskinfo?taskID=85624586 That appears to correct for me for screen blanking and when powering on an external monitor. Thanks! (In reply to Ray Strode [halfline] from comment #12) > it's a bit of a guess, but I think this build may fix the problem. Would > someone mind trying? > > https://koji.fedoraproject.org/koji/taskinfo?taskID=85624586 Great! I can confirm this fixes VM resizing and display connection/disconnection for me. I'm not able to test screen blanking, because I wasn't affected, but that's already confirmed by grumpey. So it seems this really fixes all these problems. Can someone please create a Bodhi update with this build? FEDORA-2022-978615c4b9 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-978615c4b9 FEDORA-2022-978615c4b9 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-978615c4b9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-978615c4b9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-978615c4b9 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. And what about Rawhide build? Reopening, because Rawhide is still broken. In today's prioritized bugs meeting, we rejected this as a prioritized bug as the fix has landed upstream and we are confident it will be included prior to the release of F37 https://meetbot.fedoraproject.org/fedora-meeting-1/2022-06-15/fedora_prioritized_bugs_and_issues.2022-06-15-14.00.log.html#l-62 To expand on the above, it would definitely be good to have the fix in Rawhide as well. However, Rawhide isn't particularly the target of the prioritized bugs process and since this is more of an annoying rather than a makes-it-unusable bug, we decided it didn't reach the level of being a prioritized bug. That said, the sooner Rawhide gets gdm-42.0-2 (or newer), the better. This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37. Why this was never fixed in Rawhide if the fix was presumably fine for F36? Can we get this fixed please? ~~~ $ rpm -q gdm gdm-42.0-3.fc38.x86_64 ~~~ Both of the fixes that were backported to gdm-42.0-2.fc36 are upstream and are included in the gdm-43.0-1.fc37 build that's in F37 updates-testing now (and in rawhide). Let me mark the 43.0 megaupdate as fixing this. FEDORA-2022-0bd68bbb43 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0bd68bbb43 FEDORA-2022-0bd68bbb43 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. Testing with gdm-43.0-1.fc38.x86_64, it seems to be fixed. Thx. Excellent! |