Bug 1431879
Summary: | Pre-GDM gnome-initial-setup fails to run (when no user created during install), with log WARNING: Unable to find required component 'gnome-settings-daemon' | ||||||
---|---|---|---|---|---|---|---|
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: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 26 | CC: | cschalle, fmuellner, jbicha, jstpierr, kevin, mclasen, mruckman, petersen, robatino, sgallagh, tiagomatos, yaneti | ||||
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:27 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-13 23:22:55 UTC
Created attachment 1262714 [details]
system journal from affected system (first boot after install) - use 'journalctl -f system.journal' to view
There's an upstream patch available in git, but no tarball release since then ... FWIW, I think this would fail the "last blocker at Go/No-Go" test, because the "or" phrasing suggests that it only needs to work with either the anaconda or initial-setup tools. (I wish we had metrics on how many people use g-i-s as well). I'm -1 blocker, but +1 FE (and I'd consider nominating it as a Prioritized Bug as well). I consider this to be a very serious issue, but not a release-blocking one. I don't think it boots to either (without user intervention). gnome-initial-setup-3.23.92-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e5a6d1bc2c I'm also -1 blocker (the critera has "or"), but +1 FE and I think we should really try and get this in. I believe the intended meaning of the 'or' was "so we aren't requiring a firstboot interface to appear if a user was creating during install", but I'd have to go back and check to be sure. I don't *think* it was intended to allow this kind of dodge. g-i-s still doesn't seem to start successfully with gnome-initial-setup-3.23.92-1.fc26 , though the failure mode is different: there's no rapid restarts of X, it just tries to start up once and sticks at a black screen for several minutes, then seems to fail and try again. Looking at the logs, things look a lot like https://bugzilla.gnome.org/show_bug.cgi?id=674885 : Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session[1429]: gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Sharing.desktop Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session[1429]: gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.ScreensaverProxy.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: Unrecoverable failure in required component org.gnome.SettingsDaemon.ScreensaverProxy.desktop Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.ScreensaverProxy.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session[1429]: gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.Rfkill.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.Rfkill.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Rfkill.desktop Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session[1429]: gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.PrintNotifications.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.PrintNotifications.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: Unrecoverable failure in required component org.gnome.SettingsDaemon.PrintNotifications.desktop Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session[1429]: gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session-binary[1429]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session[1429]: Unable to init server: Could not connect: Connection refused Mar 14 20:55:18 localhost-live.happyassassin.net audit[1711]: ANOM_ABEND auid=4294967295 uid=988 gid=982 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 pid=1711 comm="gnome-session-f" exe="/usr/libexec/gnome-session-failed" sig=11 res=1 Mar 14 20:55:18 localhost-live.happyassassin.net gnome-session[1429]: Unable to init server: Could not connect: Connection refused Mar 14 20:55:18 localhost-live.happyassassin.net kernel: show_signal_msg: 72 callbacks suppressed Mar 14 20:55:18 localhost-live.happyassassin.net kernel: gnome-session-f[1711]: segfault at 0 ip 00007fba153cd8d9 sp 00007ffc60809e40 error 4 in libgtk-3.so.0.2200.9[7fba150ed000+6f5000] That all happens some time after g-i-s tried to start up (which was around 20:53:39), and as you can see at the end, gnome-session-failed crashes again. We have sufficient votes for accepted FE status at present. gnome-initial-setup-3.23.92-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-e5a6d1bc2c By the way, I am able to duplicate this bug (New User mode fails to start) on Ubuntu GNOME 17.04 Beta with gnome-initial-setup 3.23.92 and gnome-settings-daemon 3.23.92. (Ubuntu GNOME does not use gnome-initial-setup's New User mode by default.) https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=e5c6735c6b did not help. I was able to workaround this by reducing the final line of /usr/share/gnome-session/sessions/gnome-initial-setup.session to RequiredComponents=setup-shell;gnome-initial-setup;org.gnome.SettingsDaemon.Keyboard;org.gnome.SettingsDaemon.Power; Obviously, that's bad as it disables accessibility support and probably some other important things. But if you need a quick workaround, maybe that will do. Discussed in today's Go/No-Go meeting. This bug is a violation of the following 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." FWIW since the last time the issue of failing session startup came up for me 3 months ago, I've been running with the dconf workaround (https://git.gnome.org/browse/dconf/commit/?id=701d19d12d4e0599340c9bd1eb2b3e25a40d780b) and I've not had it since. Yanko, ok that's a similar fix to the gnome-settings-daemon fix and that one doesn't fix Initial Setup for me either. I still see this with the latest RC1 on bare metal. So I think we should probably separate the subsequent bug into a separate report for clarity; I'll do that. This bug should track only the first cause of failure, which does indeed seem to be fixed by 3.23.92. The first part of this bug was fixed with https://git.gnome.org/browse/gnome-initial-setup/commit/?id=d2c051c12 Filed https://bugzilla.redhat.com/show_bug.cgi?id=1434154 for the follow-up issue. 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 this and https://bugzilla.redhat.com/show_bug.cgi?id=1434154 are both 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. |