FS#44749 - [gnome-shell] Session is randomly closed

Attached to Project: Arch Linux
Opened by Mateus Rodrigues Costa (CharlesAtum) - Monday, 27 April 2015, 18:46 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 26 October 2016, 08:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: My session gets randomly closed after some time of use for no apparent reason. I have logs of two times it happened: the first of them points to gnome-settings-daemon and gnome-shell failing and then Xorg segfaulting.


Additional info:
* xorg-server 1.17.1-5, gnome-shell 3.16.1-2
* Logs attached


Steps to reproduce:
1. Login to a graphical session.
2. Do whatever you normally do.
3. Wait until the session gets closed.
   logs1 (11.3 KiB)
   logs2 (48.3 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 26 October 2016, 08:44 GMT
Reason for closing:  No response
Comment by Mateus Rodrigues Costa (CharlesAtum) - Friday, 01 May 2015, 16:24 GMT
It happened a third time yesterday. New log attached.
   logs3 (5.1 KiB)
Comment by Ernesto Zorrivel (zorrivel) - Friday, 01 May 2015, 18:54 GMT
In my humble opinion, this is a duplicate of  FS#42987 .
Comment by Mateus Rodrigues Costa (CharlesAtum) - Sunday, 10 May 2015, 14:27 GMT
@zorrivel Unlikely to be a duplicate of that bug: unplugging my USB mouse and everything continues working.

Anyway I got this one more time after resuming from suspending during the night, logs attached.
   logs4 (29.1 KiB)
Comment by Ernesto Zorrivel (zorrivel) - Monday, 11 May 2015, 10:30 GMT
Sorry, Mateus - I should have elaborated better the first time. The reason I think there is something in common is this segment in your xorg log:

Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) systemd-logind: failed to take device /dev/input/event16: 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, or the network connection was broken.
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (II) Using input driver 'libinput' for ' USB OPTICAL MOUSE'
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (**) USB OPTICAL MOUSE: always reports core events
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (**) Option "Device" "/dev/input/event16"
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (II) failed to create input device '/dev/input/event16'.
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) libinput: USB OPTICAL MOUSE: Failed to create a device for /dev/input/event16
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) PreInit returned 2 for " USB OPTICAL MOUSE"
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (II) UnloadModule: "libinput"
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE)
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) Backtrace:
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x119) [0x594a29]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7f0ae105853f]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 2: /usr/lib/libc.so.6 (__strcmp_sse2_unaligned+0x1a) [0x7f0ae10b529a]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 3: /usr/lib/xorg-server/Xorg (xf86SIGIOSupported+0xa38) [0x4a1e48]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 4: /usr/lib/libdbus-1.so.3 (dbus_connection_dispatch+0x3f1) [0x7f0ae2cea5d1]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 5: /usr/lib/libdbus-1.so.3 (dbus_connection_dispatch+0x645) [0x7f0ae2ceadc5]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 6: /usr/lib/xorg-server/Xorg (config_fini+0x4c1) [0x49bb11]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 7: /usr/lib/xorg-server/Xorg (WakeupHandler+0x6b) [0x43d6cb]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 8: /usr/lib/xorg-server/Xorg (WaitForSomething+0x1c3) [0x58d983]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 9: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x111) [0x4388b1]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 10: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x41b) [0x43cbcb]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 11: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f0ae1045800]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 12: /usr/lib/xorg-server/Xorg (_start+0x29) [0x427039]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) 13: ? (?+0x29) [0x29]
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE)
Abr 26 23:56:08 mateus-arch /usr/lib/gdm/gdm-x-session[1919]: (EE) Segmentation fault at address 0x0

In your case X crashes and you fall back to gdm, which makes it look like you were randomly logged off from your GNOME session.

Maybe you don't have to physically disconnect the USB device. In my case, for example, it happens with a bluetooth device which is maybe randomly disconnected or goes to sleep.

Bottom line, I think this is a xorg bug and not something related to GNOME.
Comment by Mateus Rodrigues Costa (CharlesAtum) - Wednesday, 13 May 2015, 15:38 GMT
Ok, so looks like I am getting two different bugs that display the same symptom: Xorg segfaulting and gnome-shell being terminated with SIGTRAP, both end up with my session closed.
Attached are the two backtraces I got from the gnome-shell coredumps.
I will report the two bugs upstream soon.
   coredump-backtrace (1.5 KiB)
   coredump-backtrace2 (1.5 KiB)
Comment by Mateus Rodrigues Costa (CharlesAtum) - Sunday, 14 June 2015, 22:27 GMT
  • Field changed: Percent Complete (100% → 0%)
Actually, looks like Xorg segfaulting wasn't the only reason why the session was being closed. The other one seems to be because gnome-session lost the name org.gnome.SessionManager on the bus and then gdm-password warns that pam fails to authenticate the user and closes my session.
Comment by Mateus Rodrigues Costa (CharlesAtum) - Monday, 15 June 2015, 00:04 GMT
Ok, so I will attach the full log (starting from resume) but here is the relevant log excerpt:

Jun 14 16:09:55 mateus-arch gnome-session[2158]: WARNING: Lost name on bus: org.gnome.SessionManager
Jun 14 16:10:06 mateus-arch gnome-session[2158]: WARNING: Client '/org/gnome/SessionManager/Client5' failed to reply before timeout
Jun 14 16:10:06 mateus-arch gnome-session[2158]: WARNING: Client '/org/gnome/SessionManager/Client4' failed to reply before timeout
Jun 14 16:10:22 mateus-arch NetworkManager[788]: <info> (wlp2s0): Activation: Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jun 14 16:10:22 mateus-arch NetworkManager[788]: <info> (wlp2s0): Activation: Stage 4 of 5 (IPv6 Configure Timeout) started...
Jun 14 16:10:22 mateus-arch NetworkManager[788]: <info> (wlp2s0): Activation: Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jun 14 16:10:25 mateus-arch bluetoothd[785]: Endpoint unregistered: sender=:1.51 path=/MediaEndpoint/A2DPSource
Jun 14 16:10:25 mateus-arch bluetoothd[785]: Endpoint unregistered: sender=:1.51 path=/MediaEndpoint/A2DPSink
Jun 14 16:10:29 mateus-arch gdm-password][17022]: pam_unix(gdm-password:auth): conversation failed
Jun 14 16:10:29 mateus-arch gdm-password][17022]: pam_unix(gdm-password:auth): auth could not identify password for [mateus]
Jun 14 16:10:29 mateus-arch gdm-password][17022]: gkr-pam: no password is available for user
Jun 14 16:10:29 mateus-arch polkitd[890]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.55, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.utf8) (disconnected from bus)
Jun 14 16:10:46 mateus-arch gdm-password][2000]: pam_unix(gdm-password:session): session closed for user mateus
Jun 14 16:10:56 mateus-arch systemd-logind[777]: Removed session c2.
Jun 14 16:10:56 mateus-arch systemd[1]: Stopping User Manager for UID 1000...
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopped target Default.
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopping Default.
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopped target Basic System.
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopping Basic System.
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopped target Paths.
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopping Paths.
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopped target Sockets.
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopping Sockets.
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopped target Timers.
Jun 14 16:10:56 mateus-arch systemd[2140]: Stopping Timers.
Jun 14 16:10:56 mateus-arch systemd[2140]: Reached target Shutdown.
Jun 14 16:10:56 mateus-arch systemd[2140]: Starting Shutdown.
Jun 14 16:10:56 mateus-arch systemd[2140]: Starting Exit the Session...
Jun 14 16:10:56 mateus-arch systemd[2140]: Received SIGRTMIN+24 from PID 17509 (kill).
Jun 14 16:10:56 mateus-arch systemd[1]: Stopped User Manager for UID 1000.
Jun 14 16:10:56 mateus-arch systemd[1]: Removed slice user-1000.slice.
Jun 14 16:10:56 mateus-arch systemd[1]: Stopping user-1000.slice.
Jun 14 16:10:58 mateus-arch kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:54:e6:fc:99:e6:b0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
Jun 14 16:11:12 mateus-arch systemd[1]: Started Update man-db cache.
Jun 14 16:11:12 mateus-arch systemd[1]: Starting Update man-db cache...
Jun 14 16:11:25 mateus-arch systemd[1]: Started Update man-db cache.
Jun 14 16:11:41 mateus-arch gdm-password][18167]: pam_unix(gdm-password:session): session opened for user mateus by (uid=0)
Jun 14 16:11:41 mateus-arch systemd[1]: Created slice user-1000.slice.
Jun 14 16:11:41 mateus-arch systemd[1]: Starting user-1000.slice.
Jun 14 16:11:41 mateus-arch systemd[1]: Starting User Manager for UID 1000...
Jun 14 16:11:41 mateus-arch systemd[1]: Started Session c3 of user mateus.
Jun 14 16:11:41 mateus-arch systemd[1]: Starting Session c3 of user mateus.
Jun 14 16:11:41 mateus-arch systemd-logind[777]: New session c3 of user mateus.
Jun 14 16:11:41 mateus-arch systemd[18879]: pam_unix(systemd-user:session): session opened for user mateus by (uid=0)
Jun 14 16:11:41 mateus-arch systemd[18879]: Unit type .busname is not supported on this system.
Jun 14 16:11:41 mateus-arch systemd[18879]: Reached target Sockets.
Jun 14 16:11:41 mateus-arch systemd[18879]: Starting Sockets.
Jun 14 16:11:41 mateus-arch systemd[18879]: Reached target Timers.
Jun 14 16:11:41 mateus-arch systemd[18879]: Starting Timers.
Jun 14 16:11:41 mateus-arch systemd[18879]: Reached target Paths.
Jun 14 16:11:41 mateus-arch systemd[18879]: Starting Paths.
Jun 14 16:11:41 mateus-arch systemd[18879]: Reached target Basic System.
Jun 14 16:11:41 mateus-arch systemd[18879]: Starting Basic System.
Jun 14 16:11:41 mateus-arch systemd[18879]: Reached target Default.
Jun 14 16:11:41 mateus-arch systemd[18879]: Startup finished in 85ms.
Jun 14 16:11:41 mateus-arch systemd[18879]: Starting Default.
Jun 14 16:11:41 mateus-arch systemd[1]: Started User Manager for UID 1000.
   lost-name-bus (42.1 KiB)
Comment by Mateus Rodrigues Costa (CharlesAtum) - Monday, 15 June 2015, 11:55 GMT
Happened again, logs since resume attached but here are the pieces I think are relevant:

Jun 14 23:36:12 mateus-arch kernel: traps: polkitd[26543] general protection ip:7f98e2b6c582 sp:7fffc9769660 error:0 in libmozjs-17.0.so[7f98e2a34000+3a8000]
Jun 14 23:36:12 mateus-arch systemd[1]: polkit.service: main process exited, code=killed, status=11/SEGV
Jun 14 23:36:12 mateus-arch systemd[1]: Unit polkit.service entered failed state.
Jun 14 23:36:12 mateus-arch systemd[1]: polkit.service failed.

Jun 14 23:36:16 mateus-arch systemd[1]: Started TLP suspend/resume.
Jun 14 23:36:16 mateus-arch systemd[1]: Reached target Sleep.
Jun 14 23:36:16 mateus-arch systemd[1]: Starting Sleep.
Jun 14 23:36:16 mateus-arch systemd[1]: Starting Hibernate...
Jun 14 23:36:17 mateus-arch polkitd[14328]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Jun 14 23:36:17 mateus-arch gnome-session[26495]: PolicyKit daemon reconnected to bus.
Jun 14 23:36:17 mateus-arch gnome-session[26495]: Attempting to re-register as an authentication agent.
Jun 14 23:36:17 mateus-arch gnome-session[18896]: PolicyKit daemon disconnected from the bus.
Jun 14 23:36:17 mateus-arch gnome-session[18896]: We are no longer a registered authentication agent.
Jun 14 23:36:17 mateus-arch polkitd[14328]: Registered Authentication Agent for unix-session:c5 (system bus name :1.191 [gnome-shell --mode=gdm --wayland --display-server], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.utf8)
Jun 14 23:36:17 mateus-arch polkitd[14328]: Registered Authentication Agent for unix-session:c3 (system bus name :1.257 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.utf8)
Jun 14 23:36:17 mateus-arch gnome-session[18896]: PolicyKit daemon reconnected to bus.
Jun 14 23:36:17 mateus-arch gnome-session[18896]: Attempting to re-register as an authentication agent.
Jun 14 23:36:17 mateus-arch gnome-session[18896]: We are now a registered authentication agent.
Jun 14 23:36:17 mateus-arch gnome-session[26495]: We are now a registered authentication agent.

Jun 15 07:46:08 mateus-arch systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
Jun 15 07:46:08 mateus-arch systemd[1]: Unit systemd-journald.service entered failed state.
Jun 15 07:46:08 mateus-arch systemd[1]: systemd-journald.service failed.
Jun 15 07:46:08 mateus-arch systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
Jun 15 07:46:08 mateus-arch systemd[1]: Stopping Flush Journal to Persistent Storage...
Jun 15 07:46:08 mateus-arch systemd[1]: Listening on Journal Audit Socket.
Jun 15 07:46:08 mateus-arch systemd[1]: Starting Journal Service...
Jun 15 07:46:08 mateus-arch systemd-coredump[14672]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.d09c474939204258806c9a24a20884bb.17011.1434365124000000.lz4.
Jun 15 07:46:08 mateus-arch systemd-journal[14674]: Journal started

Jun 15 07:44:34 mateus-arch systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!

Jun 15 07:46:19 mateus-arch polkitd[14328]: Unregistered Authentication Agent for unix-session:c3 (system bus name :1.257, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.utf8) (disconnected from bus)
Jun 15 07:46:21 mateus-arch dbus[789]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 15 07:46:21 mateus-arch systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 15 07:46:28 mateus-arch gnome-session[18896]: WARNING: Lost name on bus: org.gnome.SessionManager
Jun 15 07:46:29 mateus-arch gdm-session-worker[14683]: <5>GLib-GIO: Error sending message: A conexão está fechada

Jun 15 07:47:34 mateus-arch kernel: traps: gnome-shell[14731] trap int3 ip:7fe405d45ac0 sp:7ffc2031c060 error:0
Jun 15 07:47:34 mateus-arch systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
Jun 15 07:47:34 mateus-arch systemd[1]: Unit systemd-journald.service entered failed state.
Jun 15 07:47:34 mateus-arch systemd[1]: systemd-journald.service failed.
Jun 15 07:47:34 mateus-arch systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
Jun 15 07:47:34 mateus-arch systemd[1]: Stopping Flush Journal to Persistent Storage...
Jun 15 07:47:34 mateus-arch systemd[1]: Listening on Journal Audit Socket.
Jun 15 07:47:34 mateus-arch systemd[1]: Starting Journal Service...
Jun 15 07:47:34 mateus-arch systemd-coredump[15259]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.d09c474939204258806c9a24a20884bb.14674.1434365251000000.lz4.
Jun 15 07:47:34 mateus-arch systemd-journal[15262]: Journal started
Jun 15 07:47:17 mateus-arch gnome-session[18896]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Jun 15 07:47:26 mateus-arch gdm-password][18167]: pam_unix(gdm-password:session): session closed for user mateus
Jun 15 07:47:34 mateus-arch systemd[1]: Started Journal Service.
Jun 15 07:47:28 mateus-arch systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
Jun 15 07:47:33 mateus-arch systemd-coredump[14843]: Process 14731 (gnome-shell) of user 1000 dumped core.
Jun 15 07:47:34 mateus-arch systemd[1]: Starting Flush Journal to Persistent Storage...
Jun 15 07:47:34 mateus-arch systemd[1]: Started Flush Journal to Persistent Storage.
Jun 15 07:47:44 mateus-arch gdm-password][16094]: pam_unix(gdm-password:session): session opened for user mateus by mateus(uid=0)
Jun 15 07:47:44 mateus-arch systemd-logind[777]: New session c7 of user mateus.
Jun 15 07:47:44 mateus-arch systemd[1]: Started Session c7 of user mateus.
Jun 15 07:47:44 mateus-arch systemd[1]: Starting Session c7 of user mateus.
Jun 15 07:47:45 mateus-arch /usr/lib/gdm/gdm-x-session[17161]: X.Org X Server 1.17.1
Jun 15 07:47:46 mateus-arch /usr/lib/gdm/gdm-x-session[17161]: Release Date: 2015-02-10
Jun 15 07:47:46 mateus-arch /usr/lib/gdm/gdm-x-session[17161]: X Protocol Version 11, Revision 0
Jun 15 07:47:46 mateus-arch kernel: Uhhuh. NMI received for unknown reason 3c on CPU 0.
Jun 15 07:47:47 mateus-arch kernel: Do you have a strange power saving mode enabled?
Jun 15 07:47:47 mateus-arch kernel: Dazed and confused, but trying to continue
   session-closed (53.3 KiB)
Comment by Jan Alexander Steffens (heftig) - Monday, 15 June 2015, 12:11 GMT
Seems your system is severely broken and segfaults random processes, dbus-daemon included.
Comment by Mateus Rodrigues Costa (CharlesAtum) - Monday, 15 June 2015, 14:32 GMT
Actually, I think you're probably right on that. My root partition is a btrfs filesystem and just some days ago I have noticed they added a btrfs section on the TLP page. I will do a btrfsck on / and then reinstall all non-AUR packages to see if it fixes the issues.

Also, looks like I'm not the only one having the traps in polkit with libmozjs: https://bbs.archlinux.org/viewtopic.php?id=197229

And here goes the backtrace from "Jun 15 07:47:33 mateus-arch systemd-coredump[14843]: Process 14731 (gnome-shell) of user 1000 dumped core.":
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0 0x00007fe405d45ac0 in g_logv () from /usr/lib/libglib-2.0.so.0
(gdb) bt
#0 0x00007fe405d45ac0 in g_logv () from /usr/lib/libglib-2.0.so.0
#1 0x00007fe405d45cff in g_log () from /usr/lib/libglib-2.0.so.0
#2 0x00007fe40766c6ce in meta_clutter_init () from /usr/lib/libmutter.so.0
#3 0x00007fe40769d082 in meta_init () from /usr/lib/libmutter.so.0
#4 0x0000000000401ddb in main ()

There are also several gjs-console coredumps and one gdm coredump from yesterday.

Here is the most recent gjs-console coredump. This segfault is expected because of  FS#42731  :
Core was generated by `/usr/bin/gjs-console /usr/bin/polari --gapplication-service'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fc1ed7b3f37 in ?? () from /usr/lib/libtelepathy-logger.so.3
(gdb) bt
#0 0x00007fc1ed7b3f37 in ?? () from /usr/lib/libtelepathy-logger.so.3
#1 0x00007fc1ed7bf693 in ?? () from /usr/lib/libtelepathy-logger.so.3
#2 0x00007fc208f99b0f in ?? () from /usr/lib/libgio-2.0.so.0
#3 0x00007fc208f86126 in ?? () from /usr/lib/libgio-2.0.so.0
#4 0x00007fc208faa9c5 in ?? () from /usr/lib/libgio-2.0.so.0
#5 0x00007fc20b7a3fb8 in ?? () from /usr/lib/libglib-2.0.so.0
#6 0x00007fc20b7a3625 in ?? () from /usr/lib/libglib-2.0.so.0
#7 0x00007fc2071de354 in start_thread () from /usr/lib/libpthread.so.0
#8 0x00007fc20b478bfd in clone () from /usr/lib/libc.so.6

And this one is from gdm from Dom 2015-06-14 16:36:30 BRT:
Core was generated by `/usr/bin/gdm'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000000416da0 in ?? ()
(gdb) bt
#0 0x0000000000416da0 in ?? ()
#1 0x00007fdb920221f0 in ffi_call_unix64 () from /usr/lib/libffi.so.6
#2 0x00007fdb92021c58 in ffi_call () from /usr/lib/libffi.so.6
#3 0x00007fdb9312eb04 in g_cclosure_marshal_generic () from /usr/lib/libgobject-2.0.so.0
#4 0x00007fdb9312e2f5 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#5 0x00007fdb9313ff22 in ?? () from /usr/lib/libgobject-2.0.so.0
#6 0x00007fdb93147601 in g_signal_emitv () from /usr/lib/libgobject-2.0.so.0
#7 0x0000000000429f78 in ?? ()
#8 0x00007fdb93457087 in ?? () from /usr/lib/libgio-2.0.so.0
#9 0x00007fdb9343f48c in ?? () from /usr/lib/libgio-2.0.so.0
#10 0x00007fdb92e5990d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0x00007fdb92e59ce0 in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x00007fdb92e5a002 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#13 0x000000000040b372 in ?? ()
#14 0x00007fdb9266b790 in __libc_start_main () from /usr/lib/libc.so.6
#15 0x000000000040b5f9 in ?? ()

The journal coredump doesn't appears on coredumpctl, so I will check it some other time.
Comment by Mateus Rodrigues Costa (CharlesAtum) - Monday, 29 June 2015, 20:39 GMT
I expected it wouldn't happen again after fscking the root partition and reinstalling everything, looks like I was wrong.

So, here are the logs:
-- Logs begin at Sex 2015-06-05 16:09:16 BRT, end at Seg 2015-06-29 17:18:15 BRT. --
Jun 29 17:13:18 mateus-arch gnome-session[4491]: WARNING: Lost name on bus: org.gnome.SessionManager
Jun 29 17:13:22 mateus-arch dleyna-renderer-service[30589]: Lost /com/intel/dLeynaRenderer/server/51
Jun 29 17:13:24 mateus-arch kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:54:e6:fc:99:e6:b0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
Jun 29 17:13:46 mateus-arch kernel: traps: dleyna-renderer[30589] general protection ip:7f858880c158 sp:7ffdde8e7950 error:0 in libdleyna-renderer-1.0.so.1.0.3[7f8588802000+17000]
Jun 29 17:13:46 mateus-arch kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:54:e6:fc:99:e6:b0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
Jun 29 17:13:28 mateus-arch polkitd[773]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.58, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.utf8) (disconnected from bus)
Jun 29 17:13:46 mateus-arch bluetoothd[681]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSource
Jun 29 17:13:46 mateus-arch bluetoothd[681]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSink
Jun 29 17:13:57 mateus-arch gnome-session[4491]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Jun 29 17:13:57 mateus-arch gnome-session[4491]: WARNING: App 'gnome-shell.desktop' exited with code 1
Jun 29 17:13:58 mateus-arch gdm-password][3658]: pam_unix(gdm-password:session): session closed for user mateus
Jun 29 17:14:04 mateus-arch systemd-logind[680]: Removed session c2.
Jun 29 17:14:04 mateus-arch systemd[1]: Stopping User Manager for UID 1000...
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopped target Default.
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopping Default.
Jun 29 17:14:05 mateus-arch systemd[3667]: Reached target Shutdown.
Jun 29 17:14:05 mateus-arch systemd[3667]: Starting Shutdown.
Jun 29 17:14:05 mateus-arch systemd[3667]: Starting Exit the Session...
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopped target Basic System.
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopping Basic System.
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopped target Timers.
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopping Timers.
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopped target Paths.
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopping Paths.
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopped target Sockets.
Jun 29 17:14:05 mateus-arch systemd[3667]: Stopping Sockets.
Jun 29 17:14:05 mateus-arch kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:54:e6:fc:99:e6:b0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
Jun 29 17:14:05 mateus-arch systemd-coredump[25030]: Process 30589 (dleyna-renderer) of user 1000 dumped core.
Jun 29 17:14:06 mateus-arch systemd[3667]: Received SIGRTMIN+24 from PID 25116 (kill).
Jun 29 17:14:06 mateus-arch systemd[1]: Stopped User Manager for UID 1000.
Jun 29 17:14:06 mateus-arch systemd[1]: Removed slice user-1000.slice.
Jun 29 17:14:06 mateus-arch systemd[1]: Stopping user-1000.slice.
Jun 29 17:14:06 mateus-arch systemd-logind[680]: Failed to remove runtime directory /run/user/1000: Permission denied
Jun 29 17:14:32 mateus-arch gdm-password][25183]: pam_unix(gdm-password:session): session opened for user mateus by (uid=0)
Jun 29 17:14:32 mateus-arch systemd[1]: Created slice user-1000.slice.
Jun 29 17:14:32 mateus-arch systemd[1]: Starting user-1000.slice.
Jun 29 17:14:32 mateus-arch systemd[1]: Starting User Manager for UID 1000...
Jun 29 17:14:32 mateus-arch systemd[1]: Started Session c3 of user mateus.
Jun 29 17:14:32 mateus-arch systemd-logind[680]: New session c3 of user mateus.
Jun 29 17:14:32 mateus-arch systemd[1]: Starting Session c3 of user mateus.
Jun 29 17:14:32 mateus-arch systemd[25187]: pam_unix(systemd-user:session): session opened for user mateus by (uid=0)
Jun 29 17:14:32 mateus-arch systemd[25187]: Reached target Sockets.
Jun 29 17:14:32 mateus-arch systemd[25187]: Starting Sockets.
Jun 29 17:14:32 mateus-arch systemd[25187]: Reached target Paths.
Jun 29 17:14:32 mateus-arch systemd[25187]: Starting Paths.
Jun 29 17:14:32 mateus-arch systemd[25187]: Reached target Timers.
Jun 29 17:14:32 mateus-arch systemd[25187]: Starting Timers.
Jun 29 17:14:32 mateus-arch systemd[25187]: Reached target Basic System.
Jun 29 17:14:32 mateus-arch systemd[25187]: Starting Basic System.
Jun 29 17:14:32 mateus-arch systemd[25187]: Reached target Default.
Jun 29 17:14:32 mateus-arch systemd[25187]: Startup finished in 142ms.
Jun 29 17:14:32 mateus-arch systemd[25187]: Starting Default.
Jun 29 17:14:32 mateus-arch systemd[1]: Started User Manager for UID 1000.

The backtrace of the dleyna-renderer-service coredump:
Core was generated by `/usr/lib/dleyna-renderer/dleyna-renderer-service'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f858880c158 in dlr_device_unsubscribe () from /usr/lib/dleyna-renderer/libdleyna-renderer-1.0.so.1
(gdb) bt
#0 0x00007f858880c158 in dlr_device_unsubscribe () from /usr/lib/dleyna-renderer/libdleyna-renderer-1.0.so.1
#1 0x00007f85888129da in dlr_upnp_unsubscribe () from /usr/lib/dleyna-renderer/libdleyna-renderer-1.0.so.1
#2 0x00007f858880fd57 in ?? () from /usr/lib/dleyna-renderer/libdleyna-renderer-1.0.so.1
#3 0x00007f8588d2baa8 in ?? () from /usr/lib/libdleyna-core-1.0.so.3
#4 0x00007f8588a6390d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#5 0x00007f8588a63ce0 in ?? () from /usr/lib/libglib-2.0.so.0
#6 0x00007f8588a64002 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#7 0x00007f8588d2bc8c in dleyna_main_loop_start () from /usr/lib/libdleyna-core-1.0.so.3
#8 0x0000000000400d70 in main ()

While I don't see why dleyna-renderer-service segfaulting would cause the session being closed, the fact that gnome-session once again loses org.gnome.SessionManager on bus seems to be important.

Any tips on what I should do to debug that issue?
Comment by Mateus Rodrigues Costa (CharlesAtum) - Thursday, 02 July 2015, 16:31 GMT
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=751854
Comment by Jan de Groot (JGC) - Wednesday, 12 October 2016, 13:51 GMT
Is this still a problem for you? Bug is over a year old, reported against gnome 3.16, we're at 3.22 now.

Loading...