Bug 1058047

Created attachment 855717 [details]
Excerpt from the log showing the segfaults

Getting same segfaults also.

Feb  3 16:45:53 monster kernel: [203076.185590] gnome-shell[2228]: segfault at 8 ip 00007fdfa9c84423 sp 00007fffdf6a2800 error 4 in libgnome-shell.so.#prelink#.77vZeT (deleted)[7fdfa9c58000+9d000]
Feb  4 08:17:55 monster kernel: [258976.020964] gnome-shell[28398]: segfault at 8 ip 0000003bce22c42e sp 00007fff8578e900 error 4 in libgnome-shell.so[3bce200000+9d000]
Feb  4 15:33:03 monster kernel: [285073.898032] gnome-shell[2691]: segfault at 8 ip 0000003bce22c42e sp 00007fffe993af80 error 4 in libgnome-shell.so[3bce200000+9d000]
Feb  5 11:21:09 monster kernel: [ 9876.023762] gnome-shell[2137]: segfault at 8 ip 0000003bce22c423 sp 00007fffed6c8d10 error 4 in libgnome-shell.so[3bce200000+9d000]
Feb  6 19:43:35 monster kernel: [126375.820260] gnome-shell[4134]: segfault at 8 ip 0000003bce22c423 sp 00007fff41e976e0 error 4 in libgnome-shell.so[3bce200000+9d000]

Got something similar again, some windows stop to respond, the mouse can be moved, then the gnome-shell seem to restart (upper bar goes away, and the re-appears), and the system is usable again.

This time I found the following in the log:

/var/log/messages:Mar 29 12:56:21 localhost kernel: [20581.299472] gnome-shell[1725]: segfault at 0 ip 00007fd22fc27431 sp 00007fff2895e690 error 4 in libmozjs-17.0.so[7fd22faf6000+3b3000]
/var/log/messages:Mar 29 12:56:21 localhost kernel: gnome-shell[1725]: segfault at 0 ip 00007fd22fc27431 sp 00007fff2895e690 error 4 in libmozjs-17.0.so[7fd22faf6000+3b3000]
/var/log/messages:Mar 29 21:02:46 localhost kernel: [28649.408247] gnome-shell[1770]: segfault at 0 ip 00007f820ac1c431 sp 00007fffc8d22130 error 4 in libmozjs-17.0.so[7f820aaeb000+3b3000]
/var/log/messages:Mar 29 21:02:46 localhost kernel: gnome-shell[1770]: segfault at 0 ip 00007f820ac1c431 sp 00007fffc8d22130 error 4 in libmozjs-17.0.so[7f820aaeb000+3b3000]

It also happened earlier in the month:

/var/log/messages-20140316:Mar  9 15:02:16 tux kernel: [99413.860861] gnome-shell[1762]: segfault at 10 ip 00007f813cd1c417 sp 00007fff47be49a0 error 4 in libmozjs-17.0.so[7f813cbeb000+3b3000]
/var/log/messages-20140316:Mar  9 15:02:16 tux kernel: gnome-shell[1762]: segfault at 10 ip 00007f813cd1c417 sp 00007fff47be49a0 error 4 in libmozjs-17.0.so[7f813cbeb000+3b3000]

Earlier it mentioned 'error 4 in libgnome-shell.so', now it is 'error 4 in libmozjs-17.0.so'.

Further info:

# rpm -q mozjs17
mozjs17-17.0.0-8.fc20.x86_64
# rpm -qi mozjs17 | grep Install
Install Date: Sat 21 Dec 2013 01:03:08 PM CET
# rpm -q gnome-shell
gnome-shell-3.10.4-2.fc20.x86_64
# rpm -qi gnome-shell | grep Install
Install Date: Sun 23 Mar 2014 01:01:54 PM CET

A fully updated system.

This still happens (on a fully updated system)

Jul 13 10:58:18 localhost kernel: [10356.127847] gnome-shell[1795]: segfault at 7fcaa19fc2b0 ip 00007fcaa1458e91 sp 00007fff461fc6f0 error 4 in libmozjs-17.0.so[7fcaa1327000+3b3000]
Jul 13 10:58:18 localhost kernel: gnome-shell[1795]: segfault at 7fcaa19fc2b0 ip 00007fcaa1458e91 sp 00007fff461fc6f0 error 4 in libmozjs-17.0.so[7fcaa1327000+3b3000]
Jul 14 20:50:18 tux kernel: [ 9893.544068] gnome-shell[1794]: segfault at 7f0f900fc448 ip 00007f0fefff6e91 sp 00007ffff33b73c0 error 4 in libmozjs-17.0.so[7f0fefec5000+3b3000]
Jul 14 20:50:18 tux kernel: gnome-shell[1794]: segfault at 7f0f900fc448 ip 00007f0fefff6e91 sp 00007ffff33b73c0 error 4 in libmozjs-17.0.so[7f0fefec5000+3b3000]
Jul 16 18:04:35 localhost kernel: [ 4450.575826] gnome-shell[1783]: segfault at 7f337c5fd928 ip 00007f339e4f8e91 sp 00007fff94771b50 error 4 in libmozjs-17.0.so[7f339e3c7000+3b3000]
Jul 16 18:04:35 localhost kernel: gnome-shell[1783]: segfault at 7f337c5fd928 ip 00007f339e4f8e91 sp 00007fff94771b50 error 4 in libmozjs-17.0.so[7f339e3c7000+3b3000]
Jul 19 11:26:00 localhost kernel: [ 7679.748629] gnome-shell[1767]: segfault at 7f9fb45fc470 ip 00007f9fb405fe91 sp 00007fff29490150 error 4 in libmozjs-17.0.so[7f9fb3f2e000+3b3000]
Jul 19 11:26:00 localhost kernel: gnome-shell[1767]: segfault at 7f9fb45fc470 ip 00007f9fb405fe91 sp 00007fff29490150 error 4 in libmozjs-17.0.so[7f9fb3f2e000+3b3000]

(this is on the same machine, not sure why systemd insists of changing the name of the system from time to time between tux and localhost...)

Not sure if this is a gnome-shell problem, or a problem with libmozjs.

Versions applicable:
gnome-shell-3.10.4-5.fc20.x86_64
mozjs17-17.0.0-8.fc20.x86_64

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.