You are not logged in.
Pages: 1
Hello All,
As a recent windows-hopper I am very happy with Arch (after flirting with debian on older machines before). These are the specs of my PC:
Ryzen 7 1700
Asrock B350m Pro 4
16 GB RAM
RX480 8GB
Sata SSD
The system runs fine, but seems to be logging out randomly sometimes. I am suspecting it has something to do with firefox, but I'm not sure what to do next. I run an up-to-date arch with gnome on wayland. After it logged out again I was able to get the following from the journalctl ( Pastebin ). I am using GNOME + GDM
What I tried to do:
Use linux-mainline package from AUR, since I was expecting maybe the ryzen updates + fixes in radeonSI would maybe help. (4.12rc2)
googling parts of my journalctl, however I could not find any usefull information
Using other browser, but also with chromeium it random logs out
Use X11 instead of wayland, also had log outs
My question for you guys
What exactly is the culprit for this? libgs, browser or something else?
Are there any known bugs that I missed?
What can I do to solve this issue? Any more debugging I should do?
Thank you guys in advance! In the mean time I keep -Syu'ing hoping for fixes..
Last edited by fur (2017-05-23 23:24:31)
Offline
Welcome to the arch linux forums fur.
May 24 00:53:45 ArchDesktop kernel: gnome-shell[972]: segfault at 7ffa2f6fffe8 ip 00007ffab4044ed5 sp 00007ffea16ff030 error 4 in libgjs.so.0.0.0[7ffab401a000+bc000]
May 24 00:53:45 ArchDesktop systemd[1]: Created slice system-systemd\x2dcoredump.slice.
May 24 00:53:45 ArchDesktop systemd[1]: Started Process Core Dump (PID 19788/UID 0).
May 24 00:53:45 ArchDesktop nuntius[1354]: Error reading events from display: Broken pipe
May 24 00:53:45 ArchDesktop org.gnome.Shell.desktop[972]: (EE)
May 24 00:53:45 ArchDesktop org.gnome.Shell.desktop[972]: Fatal server error:
May 24 00:53:45 ArchDesktop org.gnome.Shell.desktop[972]: (EE) failed to read Wayland events: Connection reset by peer
May 24 00:53:45 ArchDesktop org.gnome.Shell.desktop[972]: (EE)
May 24 00:53:45 ArchDesktop gnome-session[941]: gnome-session-binary[941]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Can you find the coredump info of PID 19788 using `coredumpctl info 19788`?
Offline
Welcome to the arch linux forums fur.
May 24 00:53:45 ArchDesktop kernel: gnome-shell[972]: segfault at 7ffa2f6fffe8 ip 00007ffab4044ed5 sp 00007ffea16ff030 error 4 in libgjs.so.0.0.0[7ffab401a000+bc000] May 24 00:53:45 ArchDesktop systemd[1]: Created slice system-systemd\x2dcoredump.slice. May 24 00:53:45 ArchDesktop systemd[1]: Started Process Core Dump (PID 19788/UID 0). May 24 00:53:45 ArchDesktop nuntius[1354]: Error reading events from display: Broken pipe May 24 00:53:45 ArchDesktop org.gnome.Shell.desktop[972]: (EE) May 24 00:53:45 ArchDesktop org.gnome.Shell.desktop[972]: Fatal server error: May 24 00:53:45 ArchDesktop org.gnome.Shell.desktop[972]: (EE) failed to read Wayland events: Connection reset by peer May 24 00:53:45 ArchDesktop org.gnome.Shell.desktop[972]: (EE) May 24 00:53:45 ArchDesktop gnome-session[941]: gnome-session-binary[941]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Can you find the coredump info of PID 19788 using `coredumpctl info 19788`?
I get "no coredumps found" with that command, probably because I already started a new session? Would that have the same information as the stack trace within the log?
Last edited by fur (2017-05-23 23:46:07)
Offline
I get "no coredumps found" with that command, probably because I already started a new session?
No coredumpctl is not connected to sessions. (# means run as root / use sudo) Does the following list any coredumps?
# coredumpctl
Offline
fur wrote:I get "no coredumps found" with that command, probably because I already started a new session?
No coredumpctl is not connected to sessions. (# means run as root / use sudo) Does the following list any coredumps?
# coredumpctl
sudo coredumpctl gives output
the info <pid> does not result output. However within the logs I posted there is (line 112)
May 24 00:53:46 ArchDesktop systemd-coredump[19789]: Process 972 (gnome-shell) of user 1000 dumped core.
Is that what you mean?
EDIT:
output of #coredumpctl
TIME PID UID GID SIG COREFILE EXE
Thu 2017-05-11 15:10:42 CEST 970 1000 1000 11 missing /usr/bin/gnome-shell
Fri 2017-05-12 11:52:27 CEST 616 120 120 11 missing /usr/bin/gnome-shell
Fri 2017-05-12 11:52:30 CEST 3474 120 120 11 missing /usr/bin/gnome-shell
Sat 2017-05-13 11:28:08 CEST 560 120 120 11 missing /usr/bin/gnome-shell
Sat 2017-05-13 18:11:42 CEST 1001 1000 1000 6 missing /usr/bin/gnome-shell
Sat 2017-05-13 18:12:44 CEST 5031 1000 1000 11 missing /usr/lib/firefox/firefox
Sat 2017-05-13 18:13:03 CEST 5153 1000 1000 11 missing /usr/lib/firefox/firefox
Sun 2017-05-14 12:10:31 CEST 576 120 120 11 missing /usr/bin/gnome-shell
Sun 2017-05-14 12:10:33 CEST 659 120 120 11 missing /usr/bin/gnome-shell
Sun 2017-05-14 17:38:06 CEST 1249 1000 1000 11 missing /usr/lib/tracker/tracker-extract
Sun 2017-05-14 18:12:24 CEST 870 1000 1000 11 missing /usr/bin/gnome-shell
Sun 2017-05-14 19:32:57 CEST 15720 1000 1000 6 missing /usr/lib/gvfs/gvfsd-mtp
Sun 2017-05-14 19:50:08 CEST 18072 1000 1000 11 missing /usr/lib/gvfs/gvfsd-mtp
Sun 2017-05-14 19:53:25 CEST 18021 1000 1000 11 missing /usr/bin/gedit
Sun 2017-05-14 20:46:27 CEST 21080 1000 1000 11 missing /usr/lib/gvfs/gvfsd-mtp
Sun 2017-05-14 20:48:36 CEST 21219 1000 1000 11 missing /usr/lib/gvfs/gvfsd-mtp
Mon 2017-05-15 12:15:17 CEST 872 1000 1000 6 missing /usr/bin/gnome-shell
Mon 2017-05-15 12:38:38 CEST 21073 1000 1000 6 missing /usr/bin/gnome-shell
Mon 2017-05-15 13:07:51 CEST 22723 1000 1000 6 missing /usr/bin/gnome-shell
Mon 2017-05-15 13:41:54 CEST 24518 1000 1000 6 missing /usr/bin/gnome-shell
Tue 2017-05-16 13:30:42 CEST 934 1000 1000 11 missing /usr/bin/gnome-shell
Wed 2017-05-17 12:54:04 CEST 7495 1000 1000 11 missing /usr/bin/gnome-shell
Wed 2017-05-17 13:25:47 CEST 18823 1000 1000 11 missing /usr/lib/firefox/firefox
Wed 2017-05-17 16:25:20 CEST 7020 1000 1000 5 missing /usr/lib/gnome-terminal/gnome-terminal-server
Wed 2017-05-17 16:55:23 CEST 518 0 0 11 missing /usr/bin/NetworkManager
Wed 2017-05-17 16:55:23 CEST 1483 1000 1000 11 missing /usr/bin/gnome-control-center
Wed 2017-05-17 17:40:58 CEST 883 1000 1000 11 missing /usr/bin/gnome-shell
Thu 2017-05-18 11:47:06 CEST 576 120 120 11 missing /usr/bin/gnome-shell
Thu 2017-05-18 11:47:09 CEST 850 120 120 11 missing /usr/bin/gnome-shell
Thu 2017-05-18 12:19:48 CEST 1208 1000 1000 11 missing /usr/bin/gnome-shell
Thu 2017-05-18 16:49:45 CEST 877 1000 1000 11 missing /usr/bin/gnome-shell
Fri 2017-05-19 16:02:58 CEST 2190 1000 1000 5 missing /usr/lib/gnome-terminal/gnome-terminal-server
Sat 2017-05-20 14:06:35 CEST 1094 1000 1000 6 missing /usr/bin/gnome-shell
Sun 2017-05-21 20:41:29 CEST 563 120 120 11 present /usr/bin/gnome-shell
Sun 2017-05-21 20:41:31 CEST 647 120 120 11 present /usr/bin/gnome-shell
Mon 2017-05-22 10:35:46 CEST 1017 1000 1000 11 present /usr/bin/gnome-shell
Mon 2017-05-22 21:43:54 CEST 572 120 120 11 present /usr/bin/gnome-shell
Mon 2017-05-22 23:32:08 CEST 579 120 120 11 present /usr/bin/gnome-shell
Mon 2017-05-22 23:32:10 CEST 659 120 120 11 present /usr/bin/gnome-shell
Tue 2017-05-23 17:29:09 CEST 1650 1000 1000 11 present /usr/lib/firefox/firefox
Tue 2017-05-23 17:54:54 CEST 1184 1000 1000 6 present /usr/bin/kactivitymanagerd
Tue 2017-05-23 18:06:27 CEST 1085 1000 1000 6 present /usr/bin/kactivitymanagerd
Wed 2017-05-24 00:53:46 CEST 972 1000 1000 11 present /usr/bin/gnome-shell
output of # coredump 972
PID: 972 (gnome-shell)
UID: 1000 (user)
GID: 1000 (user)
Signal: 11 (SEGV)
Timestamp: Wed 2017-05-24 00:53:45 CEST (1h 10min ago)
Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
Control Group: /user.slice/user-1000.slice/session-c2.scope
Unit: session-c2.scope
Slice: user-1000.slice
Session: c2
Owner UID: 1000 (user)
Boot ID: 95dc33c7bac14923953a24f3db675a29
Machine ID: e19de290908c4d68a363df6005b49483
Hostname: ArchDesktop
Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.95dc33c7bac14923953a24f3db675a29.972.1495580025000000000000.lz4
Message: Process 972 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 972:
#0 0x00007ffab4044ed5 n/a (libgjs.so.0)
#1 0x00007ffab216266a g_main_context_dispatch (libglib-2.0.so.0)
#2 0x00007ffab2162a20 n/a (libglib-2.0.so.0)
#3 0x00007ffab2162d42 g_main_loop_run (libglib-2.0.so.0)
#4 0x00007ffab3922d0c meta_run (libmutter-0.so.0)
#5 0x0000000000401ff7 main (gnome-shell)
#6 0x00007ffab1b76511 __libc_start_main (libc.so.6)
#7 0x000000000040212a n/a (gnome-shell)
Stack trace of thread 1044:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1057:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1040:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1054:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1052:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1059:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1042:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1058:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1049:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1036:
#0 0x00007ffab1c3867d poll (libc.so.6)
#1 0x00007ffaadf87ee1 n/a (libpulse.so.0)
#2 0x00007ffaadf796f1 pa_mainloop_poll (libpulse.so.0)
#3 0x00007ffaadf79d8e pa_mainloop_iterate (libpulse.so.0)
#4 0x00007ffaadf79e40 pa_mainloop_run (libpulse.so.0)
#5 0x00007ffaadf87e29 n/a (libpulse.so.0)
#6 0x00007ffaa322efe8 n/a (libpulsecommon-10.0.so)
#7 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#8 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1041:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1056:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1055:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1046:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1050:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1051:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1043:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 980:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffa9629f66b n/a (radeonsi_dri.so)
#2 0x00007ffa9629f397 n/a (radeonsi_dri.so)
#3 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#4 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 979:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffa9629f66b n/a (radeonsi_dri.so)
#2 0x00007ffa9629f397 n/a (radeonsi_dri.so)
#3 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#4 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 973:
#0 0x00007ffab1c3867d poll (libc.so.6)
#1 0x00007ffab21629b6 n/a (libglib-2.0.so.0)
#2 0x00007ffab2162acc g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007ffab2162b11 n/a (libglib-2.0.so.0)
#4 0x00007ffab218a295 n/a (libglib-2.0.so.0)
#5 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#6 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 976:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffa9629f66b n/a (radeonsi_dri.so)
#2 0x00007ffa9629f397 n/a (radeonsi_dri.so)
#3 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#4 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 978:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffa9629f66b n/a (radeonsi_dri.so)
#2 0x00007ffa9629f397 n/a (radeonsi_dri.so)
#3 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#4 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 981:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffa9629f66b n/a (radeonsi_dri.so)
#2 0x00007ffa9629f397 n/a (radeonsi_dri.so)
#3 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#4 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 982:
#0 0x00007ffab1c3867d poll (libc.so.6)
#1 0x00007ffab21629b6 n/a (libglib-2.0.so.0)
#2 0x00007ffab2162acc g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007ffa940ca55d n/a (libdconfsettings.so)
#4 0x00007ffab218a295 n/a (libglib-2.0.so.0)
#5 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#6 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 974:
#0 0x00007ffab1c3867d poll (libc.so.6)
#1 0x00007ffab21629b6 n/a (libglib-2.0.so.0)
#2 0x00007ffab2162d42 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007ffab2749f86 n/a (libgio-2.0.so.0)
#4 0x00007ffab218a295 n/a (libglib-2.0.so.0)
#5 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#6 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 977:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffa9629f66b n/a (radeonsi_dri.so)
#2 0x00007ffa9629f397 n/a (radeonsi_dri.so)
#3 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#4 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1045:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1047:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1048:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Stack trace of thread 1053:
#0 0x00007ffab1f07756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007ffaa4978500 PR_WaitCondVar (libnspr4.so)
#2 0x00007ffaacf64811 n/a (libmozjs-38.so)
#3 0x00007ffaa497dd8c n/a (libnspr4.so)
#4 0x00007ffab1f012e7 start_thread (libpthread.so.0)
#5 0x00007ffab1c4254f __clone (libc.so.6)
Already learning some more debugging, thank you!
Last edited by fur (2017-05-24 00:06:32)
Offline
Is the output of `sudo coredumpctl` the same as the output of `coredumpctl` I am wondering if your user is prevented from seeing some output from coredumptctl
From the coredumpctl man page
Example 3. Show information about a process that dumped core, matching
by its PID 6654# coredumpctl info 6654
PID 19788 is the first crash listed in the journal excert, 972 is later so may be the result of the first crash that is why I was more interested in 19788.
Offline
The output of 'sudo coredumpctl' and 'coredumpctl' are the same. This also means that I cannot find the coredump for pid=19788
Offline
After having this crash again today I was able to retrieve this coredump
PID: 962 (gnome-shell)
UID: 1000 (user)
GID: 1000 (user)
Signal: 6 (ABRT)
Timestamp: Wed 2017-05-24 15:53:46 CEST (21min ago)
Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
Control Group: /user.slice/user-1000.slice/session-c2.scope
Unit: session-c2.scope
Slice: user-1000.slice
Session: c2
Owner UID: 1000 (user)
Boot ID: 6cda9726cfee4bcfb95762fd81caaa97
Machine ID: e19de290908c4d68a363df6005b49483
Hostname: ArchDesktop
Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.6cda9726cfee4bcfb95762fd81caaa97.962.1495634026000000000000.lz4
Message: Process 962 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 962:
#0 0x00007fdde2027a10 raise (libc.so.6)
#1 0x00007fdde202913a abort (libc.so.6)
#2 0x00007fdde2627465 g_assertion_message (libglib-2.0.so.0)
#3 0x00007fdde26274fa g_assertion_message_expr (libglib-2.0.so.0)
#4 0x00007fdde44eec54 n/a (libgjs.so.0)
#5 0x00007fdddd3def6d n/a (libmozjs-38.so)
#6 0x00007fdddd3bb5cd n/a (libmozjs-38.so)
#7 0x00007fdddd712e90 n/a (libmozjs-38.so)
#8 0x00007fdddd73eede n/a (libmozjs-38.so)
#9 0x00007fdddd73f8c0 n/a (libmozjs-38.so)
#10 0x00007fdddd73fb0d n/a (libmozjs-38.so)
#11 0x00007fdddd73fed4 n/a (libmozjs-38.so)
#12 0x00007fdde4507f49 gjs_schedule_gc_if_needed (libgjs.so.0)
#13 0x00007fdde4507fb4 gjs_call_function_value (libgjs.so.0)
#14 0x00007fdde44e30b5 gjs_closure_invoke (libgjs.so.0)
#15 0x00007fdde44fae1c n/a (libgjs.so.0)
#16 0x00007fdde28d9f75 g_closure_invoke (libgobject-2.0.so.0)
#17 0x00007fdde28ebf82 n/a (libgobject-2.0.so.0)
#18 0x00007fdde28f4bdc g_signal_emit_valist (libgobject-2.0.so.0)
#19 0x00007fdde28f4fbf g_signal_emit (libgobject-2.0.so.0)
#20 0x00007fdde49e8a26 n/a (libgnome-shell.so)
#21 0x00007fdde31109d0 clutter_actor_get_preferred_height (libmutter-clutter-0.so)
#22 0x00007fdde31109d0 clutter_actor_get_preferred_height (libmutter-clutter-0.so)
#23 0x00007fdde49fbf34 _st_actor_get_preferred_height (libgnome-shell.so)
#24 0x00007fdde49f063b n/a (libgnome-shell.so)
#25 0x00007fdde31109d0 clutter_actor_get_preferred_height (libmutter-clutter-0.so)
#26 0x00007fdde312fd1a n/a (libmutter-clutter-0.so)
#27 0x00007fdde4a14f2a n/a (libgnome-shell.so)
#28 0x00007fdde31109d0 clutter_actor_get_preferred_height (libmutter-clutter-0.so)
#29 0x00007fdde3110cf2 clutter_actor_get_preferred_size (libmutter-clutter-0.so)
#30 0x00007fdde3141481 n/a (libmutter-clutter-0.so)
#31 0x00007fdde4a14fba n/a (libgnome-shell.so)
#32 0x00007fdde3110710 clutter_actor_get_preferred_width (libmutter-clutter-0.so)
#33 0x00007fdde3110c8a clutter_actor_get_preferred_size (libmutter-clutter-0.so)
#34 0x00007fdde3122eba clutter_actor_allocate_preferred_size (libmutter-clutter-0.so)
#35 0x00007fddddb201c8 ffi_call_unix64 (libffi.so.6)
#36 0x00007fddddb1fc2a ffi_call (libffi.so.6)
#37 0x00007fdde44e782f n/a (libgjs.so.0)
#38 0x00007fdde44e8ee4 n/a (libgjs.so.0)
#39 0x00007fdddd429cd8 n/a (libmozjs-38.so)
#40 0x00007fdddd42a845 n/a (libmozjs-38.so)
#41 0x00007fdddd68b42b n/a (libmozjs-38.so)
#42 0x00007fdde4ed2d3a n/a (n/a)
So does this mean that the issue is related to firefox?
Offline
No. gnome-shell uses the mozilla ecma engine as its scriting language (because a display & session server should always have the most complex design ...)
This is likely related to some extension/applet you're running - anything non-stock is suspicious.
There's also https://bugs.archlinux.org/task/53983 (one attachment has a matching backtrace) and that points https://bugs.archlinux.org/task/53582
Offline
Pages: 1