Description of problem: GNOME fails to load after a normal boot. Attempting to log in just drops me back to the login screen (gdm). A workaround is to drop to a vTTY, log in, and issue `gnome-session --failsafe`. I can then log in, but GNOME is not fully functional. The next step of the workaround is to log out, drop back to the vTTY, and this time issue `gnome-session`. For some reason, this second time, log in succeeds and i can load GNOME normally. It is after this second log in to GNOME (normal, not failsafe) that the problem reporter informs me that gnome-session has quit unexpectedly. Version-Release number of selected component: gnome-session-44.0-1.fc38 Additional info: reporter: libreport-2.17.11 type: CCpp reason: gnome-session-binary killed by SIGTRAP journald_cursor: s=f69ef3ff8a1d4b0daf3c887c93e3b31b;i=d8ea1d;b=942b13bf9615451993b6e4ca071cc51f;m=24e7f79;t=6001ec586271b;x=53ff1a95de21aad1 executable: /usr/libexec/gnome-session-binary cmdline: /usr/libexec/gnome-session-binary cgroup: 0::/user.slice/user-1000.slice/session-2.scope rootdir: / uid: 1000 kernel: 6.3.8-200.fc38.x86_64 package: gnome-session-44.0-1.fc38 runlevel: unknown backtrace_rating: 4 crash_function: g_settings_set_property Truncated backtrace: Thread no. 1 (6 frames) #2 g_settings_set_property at ../gio/gsettings.c:591 #3 object_set_property at ../gobject/gobject.c:1812 #4 g_object_new_internal at ../gobject/gobject.c:2291 #6 g_object_new_valist at ../gobject/gobject.c:2585 #8 g_settings_new at ../gio/gsettings.c:984 #9 _gsm_manager_get_default_session at ../gnome-session/gsm-manager.c:1515
Created attachment 1974958 [details] File: proc_pid_status
Created attachment 1974959 [details] File: maps
Created attachment 1974960 [details] File: limits
Created attachment 1974961 [details] File: open_fds
Created attachment 1974962 [details] File: mountinfo
Created attachment 1974963 [details] File: os_info
Created attachment 1974964 [details] File: cpuinfo
Created attachment 1974965 [details] File: core_backtrace
Created attachment 1974966 [details] File: dso_list
Created attachment 1974967 [details] File: environ
Created attachment 1974968 [details] File: backtrace
GDM fails to log me into GNOME unless i first drop to a vTTY, log in and issue `gnome-session --failsafe`. Afterwards, i can log in via GDM, log out, then log back in via GDM and my session works normally. This crash happens during that process. reporter: libreport-2.17.11 type: CCpp reason: gnome-session-binary killed by SIGTRAP journald_cursor: s=f69ef3ff8a1d4b0daf3c887c93e3b31b;i=1800511;b=0218945c9c1345e5b5ddb5ec9937f55a;m=1f22d76;t=6053a3442ad64;x=7f3ddf9b1aa02457 executable: /usr/libexec/gnome-session-binary cmdline: /usr/libexec/gnome-session-binary cgroup: 0::/user.slice/user-1000.slice/session-2.scope rootdir: / uid: 1000 kernel: 6.4.14-200.fc38.x86_64 package: gnome-session-44.0-1.fc38 runlevel: unknown backtrace_rating: 4 crash_function: g_settings_set_property
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.