Description of problem: I left my laptop to go handle something, and upon returning, my session had crashed and I had to log back in. Perhaps it happens when the screen locks? I've had it happen to me twice since I upgraded from Fedora 20. found this in the logs: gdm-session-wor[4681]: segfault at 10 ip 00007fef942a977c sp 00007ffff5c4bcb0 error 4 in gdm-session-worker[7fef9429d000+38000] I'm on Fedora 21 and GDM is 3.14.1 If I can provide more info (like if that crash has logged a stacktrace or something somewhere), please let me know.
Seeing the same issue on my T440s Running - gdm-3.14.1-2.fc21.x86_64 Mar 03 08:54:08 t440s kernel: gdm-session-wor[2036]: segfault at 10 ip 00007f74e11f277c sp 00007fff692ff160 error 4 in gdm-session-worker[7f74e1 Mar 03 08:54:08 t440s gnome-session[2402]: (gnome-settings-daemon:2862): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temp Mar 03 08:54:08 t440s org.a11y.atspi.Registry[2777]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Mar 03 08:54:08 t440s org.a11y.atspi.Registry[2777]: after 2325 requests (2325 known processed) with 0 events remaining. Mar 03 08:54:08 t440s bluetoothd[991]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSource
I have the same issue on my X61. After an update gdm chrashes whenever I lock the screen with the following log message. Mar 03 13:12:47 merten-laptop dbus[691]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Mar 03 13:12:47 merten-laptop dbus[691]: [system] Successfully activated service 'net.reactivated.Fprint' Mar 03 13:12:48 merten-laptop kernel: gdm-session-wor[3202]: segfault at 10 ip 00007fef634557fa sp 00007fffb3867f90 error 4 in gdm-session-worker[7fef63449000+38000] So I tried to remove fprintd, which I don't use at the moment. That solved the issue for me. Also it was updated during my last system update (0.5.1-3.fc21 to 0.6.0-1.fc21).
is everyone else using fingerprint readers as well?
Yeah, I was using a Thinkpad X1 Carbon with a fingerprint reader.
(but the fingerprint reader was disabled)
I have a fingerprint reader on my 444s, but I'm not using it. Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
I think this is connected to https://bugzilla.redhat.com/show_bug.cgi?id=1057472
Just to clarify: I am also not using the fingerprint reader.
Fresh crash today and also appears to be connected with fprintd Mar 09 11:59:37 t440s kernel: usb 1-1: USB disconnect, device number 6 Mar 09 11:59:37 t440s systemd-udevd[741]: error opening USB device 'descriptors' file Mar 09 11:59:47 t440s dbus[995]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Mar 09 11:59:47 t440s systemd[1]: Starting Fingerprint Authentication Daemon... Mar 09 11:59:47 t440s dbus[995]: [system] Successfully activated service 'net.reactivated.Fprint' Mar 09 11:59:47 t440s systemd[1]: Started Fingerprint Authentication Daemon. Mar 09 11:59:47 t440s kernel: gdm-session-wor[2682]: segfault at 10 ip 00007f4e5471977c sp 00007fffb0af8190 error 4 in gdm-session-worker[7f4e5470d000+38000] Mar 09 11:59:47 t440s gnome-session[2772]: (gnome-settings-daemon:2991): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X [root@t440s log]# systemctl status fprintd.service ● fprintd.service - Fingerprint Authentication Daemon Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static) Active: inactive (dead) Docs: man:fprintd(1) Mar 09 10:46:04 t440s fprintd[5435]: ** Message: device 0 claim status 0 Mar 09 10:46:04 t440s fprintd[5435]: ** Message: no longer monitoring fd 15 Mar 09 10:46:04 t440s fprintd[5435]: ** Message: released device 0 Mar 09 11:59:47 t440s systemd[1]: Starting Fingerprint Authentication Daemon... Mar 09 11:59:47 t440s systemd[1]: Started Fingerprint Authentication Daemon. Mar 09 11:59:55 t440s fprintd[5828]: ** Message: user 'sellis' claiming the device: 0 Mar 09 11:59:55 t440s fprintd[5828]: ** Message: now monitoring fd 15 Mar 09 11:59:56 t440s fprintd[5828]: ** Message: device 0 claim status 0 Mar 09 11:59:56 t440s fprintd[5828]: ** Message: no longer monitoring fd 15 Mar 09 11:59:56 t440s fprintd[5828]: ** Message: released device 0 Going to remove the fprint components as I'm not using them and see what happens. yum remove fprintd fprintd-pam
I have what looks like a related variation on this: 3.19.3-200.fc21.x86_64 #1 SMP Thu Mar 26 21:39:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [55285.554560] usb 1-6: reset full-speed USB device number 5 using xhci_hcd [55285.722036] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc000 [55285.722041] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc048 [55285.722043] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc090 [55285.722045] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc0d8 [55286.894275] usb 1-6: reset full-speed USB device number 5 using xhci_hcd [55287.060325] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc000 [55287.060329] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc048 [55287.060330] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc090 [55287.060331] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc0d8 [55288.164719] usb 1-6: reset full-speed USB device number 5 using xhci_hcd [55288.330859] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc000 [55288.330863] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc048 [55288.330865] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc090 [55288.330867] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030d2cc0d8 [55289.038263] gdm-session-wor[11882]: segfault at 10 ip 00007fd434c8377c sp 00007ffc02cd2340 error 4 in gdm-session-worker[7fd434c77000+38000] [55289.776184] [drm:assert_plane.constprop.85 [i915]] *ERROR* plane A assertion failure (expected on, current off) The result is that I'm dropped to the GDM login screen, losing whatever I was doing. This just happened when I was not touching my workstation. I do have a fingerprint reader but do not use it. Here is my USB setup: $ lsusb Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 17ef:1010 Lenovo Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 5986:026a Acer, Inc Bus 001 Device 007: ID 8087:07dc Intel Corp. Bus 001 Device 005: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader Bus 001 Device 011: ID 17ef:100f Lenovo Bus 001 Device 010: ID 047f:ac01 Plantronics, Inc. Savi 7xx Bus 001 Device 008: ID 046d:0a13 Logitech, Inc. Z-5 Speakers Bus 001 Device 006: ID 046d:0991 Logitech, Inc. QuickCam Pro for Notebooks Bus 001 Device 004: ID 17ef:1010 Lenovo Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 1050:0010 Yubico.com Yubikey Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Hi, Same problem here: Apr 24 11:42:38 freddy dbus[976]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Apr 24 11:42:38 freddy dbus[976]: [system] Successfully activated service 'net.reactivated.Fprint' Apr 24 11:42:38 freddy kernel: gdm-session-wor[1807]: segfault at 10 ip 00007f982c5da7fa sp 00007ffc423bffc0 error 4 in gdm-session-worker[7f982c5ce000+38000] Apr 24 11:42:38 freddy gnome-session[1921]: (gnome-settings-daemon:2005): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. gdm-3.14.2-1.fc21.x86_64 fprintd-pam-0.6.0-1.fc21.x86_64 fprintd-0.6.0-1.fc21.x86_64 I'm using the fingerprint reader.
After comment 10 I removed fprintd and have not seen this issue since.
I'm facing this same(gnome session crashes when left idle) issue on Fedora 21. <snip from dmesg> [14140.264352] gdm-session-wor[2154]: segfault at 10 ip 00007f5fb1f337fa sp 00007fff20413aa0 error 4 in gdm-session-worker[7f5fb1f27000+38000] <snip from dmesg> Some configuration information: [amit@discworld ~]$ cat /etc/fedora-release Fedora release 21 (Twenty One) [amit@discworld ~]$ uname -r 3.18.7-200.fc21.x86_64 This bug was reported on "2014-12-16" and still it's in *Open* state :(
Same problem on Fedora 22 : [204075.936708] gdm[1156]: segfault at 10 ip 00007f78689b419c sp 00007ffdc45788f0 error 4 in gdm[7f7868994000+5d000] It makes my session to crash at least once a day, severely hitting my productivity and exasperating me.
Crashes also flew away after removing all fprintd related packages.Thanks Chris (comment 10).
I see a problem like this whenever a "software update" message appears on the lock screen. I click on the icon and I reliably get a crash Nov 01 17:02:10 localhost.localdomain kernel: gdm-session-wor[1694]: segfault at 10 ip 000055cbe0c3177c sp 00007ffc0d01e090 error 4 in gdm-session-worker[55cbe0c25000+38000] This is for Linux localhost.localdomain 4.1.8-100.fc21.x86_64 #1 SMP Tue Sep 22 12:13:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux I am not using fingerprint login. I see the following messages in the log Nov 01 17:02:10 localhost.localdomain kernel: gdm-session-wor[1694]: segfault at 10 ip 000055cbe0c3177c sp 00007ffc0d01e090 error 4 in gdm-session-worker[55cbe0c25000+38000] Nov 01 17:02:10 localhost.localdomain org.gnome.Caribou.Daemon[1837]: ** (caribou:2035): WARNING **: daemon.vala:119: error in focus handler: Method "GetRole" with signature "" on interface "org.a11y.atspi.Accessible" could not be processed as object /org/a11y/atspi/accessible/4648 does not exist Nov 01 17:02:07 localhost.localdomain org.gnome.Caribou.Daemon[1837]: ** (caribou:2035): WARNING **: daemon.vala:119: error in focus handler: Method "GetRole" with signature "" on interface "org.a11y.atspi.Accessible" could not be processed as object /org/a11y/atspi/accessible/4587 does not exist Nov 01 17:02:07 localhost.localdomain dbus[755]: [system] Successfully activated service 'net.reactivated.Fprint' Nov 01 17:02:07 localhost.localdomain dbus[755]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
do you have a backtrace for that crash in abrt ?
I do not find one even though abrtd and abrt-ccpp both seem to be running and /etc/abrt/plugins/CCpp.conf (default configuration) should allow creation.
Here is today's version of the journalctl -r for another crash (seach for segfault below). It looks like the abrt process may die at the same time so maybe that's why there is nothing reported. Possible consequence of uid < 1000? ------------------------------------------------------------------- Nov 03 18:45:18 localhost.localdomain systemd-logind[754]: Removed session c1. Nov 03 18:45:18 localhost.localdomain gnome-session[1788]: (evolution-alarm-notify:2153): Gdk-WARNING **: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 03 18:45:18 localhost.localdomain gnome-session[1788]: seapplet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 03 18:45:18 localhost.localdomain gnome-session[1788]: (abrt:2166): Gdk-WARNING **: abrt: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 03 18:45:18 localhost.localdomain gnome-session[1788]: (org.gnome.Software:2152): Gdk-WARNING **: org.gnome.Software: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 03 18:45:18 localhost.localdomain gnome-session[1788]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Nov 03 18:45:18 localhost.localdomain gnome-keyring-daemon[1721]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Nov 03 18:45:18 localhost.localdomain org.gtk.vfs.Daemon[1822]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Nov 03 18:45:18 localhost.localdomain org.gtk.vfs.Daemon[1822]: A connection to the bus can't be made Nov 03 18:45:18 localhost.localdomain org.a11y.Bus[1822]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Nov 03 18:45:18 localhost.localdomain org.a11y.atspi.Registry[1868]: after 16297 requests (16297 known processed) with 0 events remaining. Nov 03 18:45:18 localhost.localdomain gnome-session[1788]: (gnome-settings-daemon:1912): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 03 18:45:18 localhost.localdomain org.a11y.atspi.Registry[1868]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Nov 03 18:45:18 localhost.localdomain bluetoothd[735]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink Nov 03 18:45:18 localhost.localdomain bluetoothd[735]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource Nov 03 18:45:18 localhost.localdomain kernel: gdm-session-wor[1685]: segfault at 10 ip 00005621efe3677c sp 00007ffc7f87a350 error 4 in gdm-session-worker[5621efe2a000+38000] Nov 03 18:45:18 localhost.localdomain org.gnome.Caribou.Daemon[1822]: ** (caribou:2033): WARNING **: daemon.vala:119: error in focus handler: Method "GetRole" with signature "" on interface "org.a11y.atspi.Accessible" could not be processed as object /org/a11y/atspi/accessible/5390 does not exist Nov 03 18:45:15 localhost.localdomain gdm-password][4024]: gkr-pam: no password is available for user Nov 03 18:45:15 localhost.localdomain gdm-password][4024]: pam_succeed_if(gdm-password:auth): requirement "uid >= 1000" not met by user "dfc" Nov 03 18:45:15 localhost.localdomain gdm-password][4024]: pam_unix(gdm-password:auth): auth could not identify password for [dfc] Nov 03 18:45:15 localhost.localdomain gdm-password][4024]: pam_unix(gdm-password:auth): conversation failed Nov 03 18:45:15 localhost.localdomain org.gnome.Caribou.Daemon[1822]: ** (caribou:2033): WARNING **: daemon.vala:119: error in focus handler: Method "GetRole" with signature "" on interface "org.a11y.atspi.Accessible" could not be processed as object /org/a11y/atspi/accessible/5329 does not exist Nov 03 18:45:15 localhost.localdomain org.gnome.Caribou.Daemon[1822]: ** (caribou:2033): WARNING **: daemon.vala:119: error in focus handler: Method "GetRole" with signature "" on interface "org.a11y.atspi.Accessible" could not be processed as object /org/a11y/atspi/accessible/5284 does not exist Nov 03 18:45:15 localhost.localdomain gdm-password][4016]: gkr-pam: no password is available for user Nov 03 18:45:15 localhost.localdomain gdm-password][4016]: pam_succeed_if(gdm-password:auth): requirement "uid >= 1000" not met by user "dfc" Nov 03 18:45:15 localhost.localdomain gdm-password][4016]: pam_unix(gdm-password:auth): auth could not identify password for [dfc] Nov 03 18:45:15 localhost.localdomain gdm-password][4016]: pam_unix(gdm-password:auth): conversation failed Nov 03 18:45:15 localhost.localdomain fprintd[3992]: ** Message: released device 0 Nov 03 18:45:15 localhost.localdomain fprintd[3992]: ** Message: no longer monitoring fd 15 Nov 03 18:45:15 localhost.localdomain fprintd[3992]: ** Message: device 0 claim status 0 Nov 03 18:45:15 localhost.localdomain fprintd[3992]: ** Message: now monitoring fd 15 Nov 03 18:45:15 localhost.localdomain fprintd[3992]: ** Message: user 'dfc' claiming the device: 0 Nov 03 18:45:13 localhost.localdomain gdm-password][4006]: gkr-pam: no password is available for user Nov 03 18:45:13 localhost.localdomain gdm-password][4006]: pam_succeed_if(gdm-password:auth): requirement "uid >= 1000" not met by user "dfc" Nov 03 18:45:13 localhost.localdomain gdm-password][4006]: pam_unix(gdm-password:auth): auth could not identify password for [dfc] Nov 03 18:45:13 localhost.localdomain gdm-password][4006]: pam_unix(gdm-password:auth): conversation failed Nov 03 18:45:13 localhost.localdomain fprintd[3992]: ** Message: released device 0 Nov 03 18:45:13 localhost.localdomain fprintd[3992]: ** Message: no longer monitoring fd 15 Nov 03 18:45:13 localhost.localdomain org.gnome.Caribou.Daemon[1822]: ** (caribou:2033): WARNING **: daemon.vala:119: error in focus handler: Method "GetRole" with signature "" on interface "org.a11y.atspi.Accessible" could not be processed as object /org/a11y/atspi/accessible/5222 does not exist Nov 03 18:45:13 localhost.localdomain org.gnome.Caribou.Daemon[1822]: ** (caribou:2033): WARNING **: daemon.vala:119: error in focus handler: Method "GetRole" with signature "" on interface "org.a11y.atspi.Accessible" could not be processed as object /org/a11y/atspi/accessible/5222 does not exist Nov 03 18:45:13 localhost.localdomain fprintd[3992]: ** Message: device 0 claim status 0 Nov 03 18:45:13 localhost.localdomain fprintd[3992]: ** Message: now monitoring fd 15 Nov 03 18:45:12 localhost.localdomain fprintd[3992]: ** Message: user 'dfc' claiming the device: 0 Nov 03 18:45:10 localhost.localdomain org.gnome.Caribou.Daemon[1822]: ** (caribou:2033): WARNING **: daemon.vala:119: error in focus handler: Method "GetRole" with signature "" on interface "org.a11y.atspi.Accessible" could not be processed as object /org/a11y/atspi/accessible/5144 does not exist Nov 03 18:45:09 localhost.localdomain dbus[755]: [system] Successfully activated service 'net.reactivated.Fprint' Nov 03 18:45:09 localhost.localdomain dbus[755]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Nov 03 18:18:31 localhost.localdomain org.gnome.Caribou.Daemon[1822]: ** (caribou:2033): WARNING **: daemon.vala:119: error in focus handler: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, Nov 03 18:01:01 localhost.localdomain systemd[3774]: pam_unix(systemd-user:session): session closed for user root Nov 03 18:01:01 localhost.localdomain systemd[3768]: Received SIGRTMIN+24 from PID 3801 (kill). Nov 03 18:01:01 localhost.localdomain systemd[3768]: Starting Exit the Session... Nov 03 18:01:01 localhost.localdomain systemd[3768]: Reached target Shutdown. Nov 03 18:01:01 localhost.localdomain systemd[3768]: Starting Shutdown. Nov 03 18:01:01 localhost.localdomain systemd[3768]: Stopped target Sockets. Nov 03 18:01:01 localhost.localdomain systemd[3768]: Stopping Sockets. Nov 03 18:01:01 localhost.localdomain systemd[3768]: Stopped target Timers. Nov 03 18:01:01 localhost.localdomain systemd[3768]: Stopping Timers. Nov 03 18:01:01 localhost.localdomain systemd[3768]: Stopped target Paths. Nov 03 18:01:01 localhost.localdomain systemd[3768]: Stopping Paths. Nov 03 18:01:01 localhost.localdomain systemd[3768]: Stopped target Basic System.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.