Hide Forgot
Description of problem: The first attempt to log in after bootup results in just getting kicked back to the login screen. The second attempt seems to work. Some output in journalctl seems to indicate that gnome-settings-daemon is getting a "Failed to initialize GTK+" error and then eventually segfaulting (possibly after a restart attempt). This is under Wayland. Unfortunately I'm not getting any ABRT crash notifications, etc, possibly as a result of bug 1371709. Version-Release number of selected component (if applicable): gnome-settings-daemon-3.22.1-1.fc25.x86_64 How reproducible: Every time on this machine Steps to Reproduce: 1. Boot up 2. Log in 3. Actual results: In journalctl: Nov 23 18:10:14 eng1n65.eng.sedsystems.ca gnome-settings-[2088]: Unable to initialize GTK+ Nov 23 18:10:14 eng1n65.eng.sedsystems.ca gnome-session[2044]: gnome-session-binary[2044]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1 Nov 23 18:10:14 eng1n65.eng.sedsystems.ca gnome-session-binary[2044]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1 Nov 23 18:10:14 eng1n65.eng.sedsystems.ca gnome-settings-[2098]: Unable to initialize GTK+ Nov 23 18:10:14 eng1n65.eng.sedsystems.ca gnome-session[2044]: gnome-session-binary[2044]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1 Nov 23 18:10:14 eng1n65.eng.sedsystems.ca gnome-session-binary[2044]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1 Nov 23 18:10:14 eng1n65.eng.sedsystems.ca gnome-session[2044]: gnome-session-binary[2044]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly Nov 23 18:10:14 eng1n65.eng.sedsystems.ca gnome-session-binary[2044]: Unrecoverable failure in required component gnome-settings-daemon.desktop Nov 23 18:10:14 eng1n65.eng.sedsystems.ca gnome-session-binary[2044]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly Nov 23 18:10:14 eng1n65.eng.sedsystems.ca kernel: show_signal_msg: 174 callbacks suppressed Nov 23 18:10:14 eng1n65.eng.sedsystems.ca kernel: gnome-session-f[2108]: segfault at 0 ip 00007f1a65c1e229 sp 00007ffeaca25540 error 4 in libgtk-3.so.0.2200.2[7f1a65940000+6f0000] Nov 23 18:10:14 eng1n65.eng.sedsystems.ca systemd[1]: Created slice system-systemd\x2dcoredump.slice. Nov 23 18:10:14 eng1n65.eng.sedsystems.ca systemd[1]: Started Process Core Dump (PID 2112/UID 0). Nov 23 18:10:14 eng1n65.eng.sedsystems.ca audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-2112-0 comm="syste Expected results: No crashes Additional info:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I'm seeing these symptoms on a system with gnome-settings-daemon-3.22.2-1.fc25.x86_64. The problem manifests on a system that has been upgraded to fedora25 from fedora24 but not on a similar system that has had a fresh install of fedora25. I'm able to avoid the problem by logging in as a newly created user on the upgraded fedora25 system. I have been unable to find the lingering configuration on my main user account that is causing this.
Can one of you please edit your /etc/gdm/custom.conf and enable debug: [debug] # Uncomment the line below to turn on debugging Enable=true and then attach here the full journalctl output for a login attempts where this happens?
And check whether there is a file under: ~/.config/gnome-session/saved-session/ before a login failure.
Created attachment 1294668 [details] output of journalctl -u gdm -e after enabling debug logging The problem no longer manifests for me after I removed lots of old dotfile config from my home directory. But I'm still attaching the logs so someone else can compare to see what normal looks like.
(In reply to rday from comment #5) > Created attachment 1294668 [details] > output of journalctl -u gdm -e after enabling debug logging We need the *full* log. This is just the gdm user's. > The problem no longer manifests for me after I removed lots of old dotfile > config from my home directory. But I'm still attaching the logs so someone > else can compare to see what normal looks like. Well, if this isn't a log of a failing attempt it's not useful.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.