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 1194948
Summary: | gnome-initial-setup fails to start after Fedora 22 Workstation 2015-02-18 install | ||||||
---|---|---|---|---|---|---|---|
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: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 22 | CC: | danofsatx, jmccann, maurizio.antillon, normand, robatino, rstrode, znmeb | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | AcceptedBlocker | ||||||
Fixed In Version: | gdm-3.15.91-1.fc22 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-03-03 04:20:23 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: | 1043121 | ||||||
Attachments: |
|
Description
Adam Williamson
2015-02-21 01:25:59 UTC
Created attachment 994071 [details]
full journal log from an affected boot
This does seem limited to the pre-GDM, user-creating version of g-i-s, because if I create a user in anaconda, the installed system boots successfully to GDM and subsequently successfully launches the user's session. This is the xserver bug I was telling you about a couple of days ago on irc. Dave commited a fix, but gcc5 ICEs so we can't get the fix into the compose. there's a thread on fedora-devel-list about it. Still, I'm firing off a build now to see if the gcc problem has resolved itself since the 17th when Dave did his build attempts. Actually, though, yesterday I changed the way we launch X servers from GDM (as part of the wayland work), and a side effect of that work is that we don't depend on the functionality that was broken in the X server anymore, anyway. So this bug should be resolved one way or another going forward. The xserver build succeeded,, but the new GDM code I alluded to in comment 3 actually broke launching gnome-initial-setup. I'm going to co-opt this bug for that problem. by all means co-opt whatever you darn well please if it means things will get fixed ;) Discussed at today's blocker review meeting [1]. AcceptedBlocker Alpha - This bug is a clear violation of the Alpha criterion: "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility." http://meetbot.fedoraproject.org/fedora-blocker-review/2015-02-23/ I think this should be square now Can you please submit an update for it? Bodhi is now active for F22. Thanks! gdm-3.15.90.5-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/gdm-3.15.90.5-1.fc22 Package gdm-3.15.90.5-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gdm-3.15.90.5-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2550/gdm-3.15.90.5-1.fc22 then log in and leave karma (feedback). gdm-3.15.91-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/gdm-3.15.91-1.fc22 gdm-3.15.91-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |