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 1434154
Summary: | Pre-GDM gnome-initial-setup fails to run (when no user created during install), with multiple "Unrecoverable failure in required component" errors | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||
Component: | gnome-initial-setup | Assignee: | Rui Matos <tiagomatos> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 26 | CC: | jbicha, jstpierr, mboddu, robatino, tflink, tiagomatos | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | AcceptedBlocker | ||||||
Fixed In Version: | gnome-initial-setup-3.24.0-1.fc26 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-03-24 21:53:20 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-20 20:12:49 UTC
Proposing as an Alpha blocker on the same rationale as https://bugzilla.redhat.com/show_bug.cgi?id=1431879 , which was accepted as a blocker: violates "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" in the case of an install without creating a user. Created attachment 1264850 [details]
journal from a VM test where g-i-s start failed five times then succeeded
Adam, I'm using Ubuntu GNOME 17.04 with GNOME 3.23.92/3.24 and Initial Setup's New User mode fails for me every time (even with the patches proposed so far to GNOME #674885). I mentioned an ugly workaround at https://bugzilla.redhat.com/1431879#c11 I haven't noticed Initial Setup being broken for existing users. It's easy to test; just remove ~/.config/gnome-initial-setup-done Initial Setup will then pop up every time you log in until you click through to complete Initial Setup. Yes, I already know the version of g-i-s that runs on first log in to a user account isn't broken, and I wouldn't expect it to be, because running i-s in an existing user's session doesn't involve session startup. This mode is failing during session startup. It does seem interesting that, so far, the g-i-s session startup seems much more prone to failure than a regular user session, but I want to do a bit more testing to be totally sure of that. +1 blocker from me, for the criterion mentioned in c#1 and the reasoning +1 blocker +1 Blocker That's +4 blocker (including me), setting accepted. We think we have a fix for this (rtcm found it, I tried it and it works for me), build coming soon. gnome-initial-setup-3.24.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-559925b8d4 gnome-initial-setup-3.24.0-1.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-559925b8d4 Confirmed fixed in Alpha RC2. gnome-initial-setup-3.24.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |