Bug 1435010
| Summary: | GNOME fails to start without modesetting (Fedora 'basic graphics') mode | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 26 | CC: | ajax, fmuellner, jadahl, klember, mruckman, otaylor, pbrobinson, rmatos, robatino, rstrode, sgallagh, walters | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | AcceptedBlocker | ||||||
| Fixed In Version: | gdm-3.24.0-2.fc26 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-03-29 05:05:33 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: | 1349184 | ||||||
| Attachments: |
|
||||||
|
Description
Adam Williamson
2017-03-22 21:48:37 UTC
Created attachment 1265502 [details]
full journal contents
This message seems to come from mutter, so maybe that's the right component... +1 blocker. I also see this on a macbook here. Comparing to F25, this same thing actually seems to happen on the *first* login attempt there; it also boots to GDM (instead of booting straight to the desktop), and similar messages are present in the journal. But if you then click 'Live System User' in gdm, it logs in fine, and the errors don't seem to be present for that session. +1 as well for blocker. +1 to block. I've also seen it on a custom system I have at home with a too-new GeForce card. Adding some people to CC who might be able to help with this. Discussed at 2017-03-23 Fedora 26 Alpha Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-2/2017-03-23/f26-alpha-go-no-go-meeting-2nd.2017-03-23-17.00.log.txt . Accepted as a blocker per the cited criterion footnote. Adding rtcm and jadahl who mclasen thought could help. Still happens with GNOME 3.24.0 and kernel rc3.git0.2 , FWIW. logs show gdm misbehaving, though I haven't quite figured out why yet. reassigning. i think I see the problem now, but I haven't tested a fix yet. This commit, changes the way list of session dirs is computed from a static list to something dynamically generated: https://git.gnome.org/browse/gdm/commit/?id=5b1e625417c274823c66a552f37d912986fc34d8 The problem is it caches the results too aggressively, so the wayland dirs don't get pruned when the ignore-wayland flag is set. Easy fix is to just skip caching altogether, it's not really necessary. gdm-3.24.0-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-ca9825d5a2 Thanks a lot for figuring this out! I just threw together a live image including the gdm build, and it now acts like F25 (initially boots to GDM, but can log in by clicking Live System User). Will check that it works post-install too then fire an RC3 request. Thanks! gdm-3.24.0-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-ca9825d5a2 gdm-3.24.0-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |