Red Hat Bugzilla – Bug 1392970
gnome-session-failed segfaults on hard GDM service stop
Last modified: 2017-08-01 18:57:55 EDT
Version-Release number of selected component: gnome-session-3.22.1-1.el7 Additional info: reporter: libreport-2.1.11.1 backtrace_rating: 4 cmdline: /usr/libexec/gnome-session-failed --debug --allow-logout crash_function: _gtk_style_provider_private_get_settings executable: /usr/libexec/gnome-session-failed global_pid: 21790 kernel: 3.10.0-514.el7.x86_64 pkg_vendor: Fedora Project COPR (klember/rhel-7-gnome-3-22) reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 42 Truncated backtrace: Thread no. 1 (10 frames) #0 _gtk_style_provider_private_get_settings at /lib64/libgtk-3.so.0 #1 gtk_css_value_initial_compute at /lib64/libgtk-3.so.0 #2 gtk_css_static_style_compute_value at /lib64/libgtk-3.so.0 #3 _gtk_css_lookup_resolve at /lib64/libgtk-3.so.0 #4 gtk_css_static_style_new_compute at /lib64/libgtk-3.so.0 #5 gtk_css_static_style_get_default at /lib64/libgtk-3.so.0 #6 gtk_css_node_init at /lib64/libgtk-3.so.0 #7 g_type_create_instance at gtype.c:1860 #8 g_object_new_internal at gobject.c:1783 #11 gtk_css_widget_node_new at /lib64/libgtk-3.so.0
Created attachment 1218563 [details] File: backtrace
Created attachment 1218564 [details] File: cgroup
Created attachment 1218565 [details] File: core_backtrace
Created attachment 1218566 [details] File: dso_list
Created attachment 1218567 [details] File: environ
Created attachment 1218568 [details] File: exploitable
Created attachment 1218569 [details] File: limits
Created attachment 1218570 [details] File: machineid
Created attachment 1218571 [details] File: maps
Created attachment 1218572 [details] File: open_fds
Created attachment 1218573 [details] File: proc_pid_status
Created attachment 1218574 [details] File: var_log_messages
This happens on shutting down the session forcibly e.g. with: systemctl stop gdm.service A FAF report has also been created for this issue, that contains more info: http://faf.lab.eng.brq.redhat.com/faf/reports/2421/ A local machine reproducer journal excerpt: Mar 16 11:31:54 localhost systemd: Stopping GNOME Display Manager... Mar 16 11:31:54 localhost journal: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 16 11:31:54 localhost journal: nautilus-desktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 16 11:31:54 localhost journal: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 16 11:31:54 localhost journal: abrt: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 16 11:31:54 localhost gnome-session-binary[5291]: WARNING: Lost name on bus: org.gnome.SessionManager Mar 16 11:31:54 localhost journal: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 16 11:31:54 localhost gnome-session: gnome-session-binary[5291]: WARNING: Lost name on bus: org.gnome.SessionManager Mar 16 11:31:54 localhost sealertauto.desktop: seapplet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 16 11:31:54 localhost spice-vdagentd: closed vdagent virtio channel Mar 16 11:31:54 localhost journal: gnome-software: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost tracker-miner-fs.desktop: Received signal:15->'Terminated' Mar 16 11:31:54 localhost journal: Error while sending AddMatch() message: The connection is closed Mar 16 11:31:54 localhost journal: Error while sending AddMatch() message: The connection is closed Mar 16 11:31:54 localhost journal: Error while sending AddMatch() message: The connection is closed Mar 16 11:31:54 localhost tracker-miner-fs.desktop: OK Mar 16 11:31:54 localhost gnome-session-binary[5291]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Mar 16 11:31:54 localhost gnome-session: gnome-session-binary[5291]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost journal: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Mar 16 11:31:54 localhost kernel: gnome-session-f[6253]: segfault at 0 ip 00007f666226bc99 sp 00007fff82b7fe70 error 4 in libgtk-3.so.0.2200.10[7f6661f82000+6f4000] Mar 16 11:31:54 localhost gnome-session-binary[5291]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1 Mar 16 11:31:54 localhost gnome-session: gnome-session-binary[5291]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1 Mar 16 11:31:54 localhost gnome-session: gnome-session-binary[5291]: WARNING: App 'nautilus-classic.desktop' exited with code 1 Mar 16 11:31:54 localhost tracker-miner-apps.desktop: Received signal:15->'Terminated' Mar 16 11:31:54 localhost tracker-miner-apps.desktop: OK Mar 16 11:31:54 localhost gnome-session-binary[5291]: WARNING: App 'nautilus-classic.desktop' exited with code 1 Mar 16 11:31:54 localhost abrt-hook-ccpp: Process 6253 (gnome-session-failed) of user 1000 killed by SIGSEGV - dumping core Mar 16 11:31:54 localhost tracker-extract.desktop: Received signal:15->'Terminated' Mar 16 11:31:54 localhost tracker-miner-user-guides.desktop: Received signal:15->'Terminated' Mar 16 11:31:54 localhost tracker-miner-user-guides.desktop: OK Mar 16 11:31:54 localhost journal: Unable to initialize Clutter: Unable to open display ':0' Mar 16 11:31:54 localhost journal: Unable to initialize Clutter. Mar 16 11:31:54 localhost gnome-session-binary[5291]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Mar 16 11:31:54 localhost gnome-session-binary: Unrecoverable failure in required component org.gnome.Shell.desktop Mar 16 11:31:54 localhost gnome-session: gnome-session-binary[5291]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Mar 16 11:31:54 localhost gnome-session: gnome-session-binary[5291]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Mar 16 11:31:54 localhost gnome-session-binary[5291]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Mar 16 11:31:54 localhost kernel: gnome-session-f[6268]: segfault at 0 ip 00007f34a79abc99 sp 00007fffb3287270 error 4 in libgtk-3.so.0.2200.10[7f34a76c2000+6f4000] Mar 16 11:31:54 localhost gdm: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed Mar 16 11:31:54 localhost abrt-hook-ccpp: Process 6268 (gnome-session-failed) of user 1000 killed by SIGSEGV - ignoring (repeated crash) Mar 16 11:31:54 localhost gdm: (gdm-display.c:1176):gdm_display_dispose: runtime check failed: (self->priv->access_file == NULL) Mar 16 11:31:54 localhost gdm: Child process 6256 was already dead. Mar 16 11:31:54 localhost systemd: Stopped GNOME Display Manager. Mar 16 11:31:54 localhost abrt-hook-ccpp: Saved core dump of pid 6268 to core.6268 at /home/test (1847296 bytes) Mar 16 11:31:54 localhost abrt-server: Package 'gnome-session' isn't signed with proper key Mar 16 11:31:54 localhost abrt-server: 'post-create' on '/var/spool/abrt/ccpp-2017-03-16-11:31:54-6253' exited with 1 Mar 16 11:31:54 localhost abrt-server: Deleting problem directory '/var/spool/abrt/ccpp-2017-03-16-11:31:54-6253' Mar 16 11:31:57 localhost systemd-logind: Removed session 13. Mar 16 11:31:57 localhost systemd: Removed slice user-1000.slice. Mar 16 11:31:57 localhost systemd: Stopping user-1000.slice.
Created attachment 1268884 [details] backtrace
Such output was detected on nearly all Intel test platforms with RHEL7.4-alpha (3.10.0-657 kernel), which was not seen with RHEL7.3: [18685.973511] gnome-session-f[6582]: segfault at 0 ip 00007f5e7fcfbc99 sp 00007fff8dde9300 error 4 in libgtk-3.so.0.2200.10[7f5e7fa12000+6f4000]
*** Bug 1397773 has been marked as a duplicate of this bug. ***
*** Bug 1436758 has been marked as a duplicate of this bug. ***
Ray, could you please share the root cause details that cause the issue and how it was fixed? Thanks, Nanda
This particular crash is in the session failure dialog (often called the "fail whale"). The session failure dialog is presented when one or more required components of the session could not be started. I believe a crash in the X server was leading to GNOME shell and gnome-settings-daemon exiting and failing to restart (because the X server is no longer running). This lead gnome-session to try to show the session failure dialog, but, of course, without an X server it can't display the dialog either. Rather than silently exiting, a bug in error handling lead to the session failure dialog crashing if the X server was unavailable. So this report is a secondary problem report. Various primary bugs could lead this this crash occurring. # abrt-cli list may list a crash from the X server. Can you post the output of that command here?
*** Bug 1449380 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2128