After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 783723 - Segfault in libgjs.so
Segfault in libgjs.so
Status: RESOLVED DUPLICATE of bug 781799
Product: gjs
Classification: Bindings
Component: general
1.48.x
Other Linux
: Normal normal
: ---
Assigned To: gjs-maint
gjs-maint
Depends on:
Blocks:
 
 
Reported: 2017-06-13 04:08 UTC by David Li
Modified: 2017-06-13 05:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Full syslog around event. (22.92 KB, text/plain)
2017-06-13 04:08 UTC, David Li
Details

Description David Li 2017-06-13 04:08:14 UTC
Created attachment 353649 [details]
Full syslog around event.

A random segfault crashed my gnome session and logged me out while I left my system on overnight.  There was no user activity at this time, though the nice round time makes me think a scheduled task was involved.

System:
  Arch Linux amd64 (Fully updated as of Jun 12, 2017).
  i7-7700K, GTX1070 (Nvidia drivers, but using primus with i915. Display is connected to integrated graphics port)
  GNOME Shell 3.24.2 (Wayland)
  gjs 1.48.3

Relevant packages:
  gjs 1.48.3-1
  gnome-desktop 1:3.24.2-1
  gnome-session 3.24.1-1
  gnome-shell 3.24.2-1
  wayland 1.13.0-1
  wayland-protocols 1.7-1
  xorg-server 1.19.3-2
  xorg-server-common 1.19.3-2
  xorg-server-xwayland 1.19.3-2


Full syslog around the crash is attached.  I also have a core dump, which I have not uploaded as I'm unsure of what sensitive information may be contained within.  I can share the file directly with gnome developers if needed.

Dump of relevant thread is:

Jun 12 05:00:01 rdlp2 systemd-coredump[18942]: Process 3142 (gnome-shell) of user 1000 dumped core.
                                               
                                               Stack trace of thread 3142:
                                               #0  0x00007f366ca2bed5 n/a (libgjs.so.0)
                                               #1  0x00007f366ab468b5 g_main_context_dispatch (libglib-2.0.so.0)
                                               #2  0x00007f366ab46c78 n/a (libglib-2.0.so.0)
                                               #3  0x00007f366ab46f92 g_main_loop_run (libglib-2.0.so.0)
                                               #4  0x00007f366c309fdc meta_run (libmutter-0.so.0)
                                               #5  0x0000000000401ff7 main (gnome-shell)
                                               #6  0x00007f366a55943a __libc_start_main (libc.so.6)
                                               #7  0x000000000040212a n/a (gnome-shell)
                                               
                                               Stack trace of thread 3143:
                                               #0  0x00007f366a61c2bd poll (libc.so.6)
                                               #1  0x00007f366ab46bf9 n/a (libglib-2.0.so.0)
                                               #2  0x00007f366ab46d0c g_main_context_iteration (libglib-2.0.so.0)

[...]
Jun 12 05:00:01 rdlp2 kernel: gnome-shell[3142]: segfault at 7f35d94fffe8 ip 00007f366ca2bed5 sp 00007ffde566f800 error 4 in libgjs.so.0.0.0[7f366ca01000+bc000]
Comment 1 Philip Chimento 2017-06-13 05:01:11 UTC
Thanks for taking the time to report this. There's an identical stack trace on bug 781799. It's not 100% guaranteed the same bug, but it's hard to tell unless you can get a stack trace with debug symbols. I'm assuming it's a duplicate for now.

*** This bug has been marked as a duplicate of bug 781799 ***