Red Hat Bugzilla – Bug 1005299
[abrt] gnome-shell-3.9.91-1.fc21: send_frame_messages_timeout: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
Last modified: 2016-07-19 06:21:07 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (2 frames)
#0 send_frame_messages_timeout at /lib/libmutter.so.0
#6 meta_run at /lib/libmutter.so.0
Created attachment 794828 [details]
Created attachment 794829 [details]
Created attachment 794830 [details]
Created attachment 794831 [details]
Created attachment 794832 [details]
Created attachment 794833 [details]
Created attachment 794834 [details]
Created attachment 794835 [details]
Created attachment 794836 [details]
Created attachment 794837 [details]
Created attachment 794838 [details]
*** Bug 1013346 has been marked as a duplicate of this bug. ***
Should be fixed upstream by https://git.gnome.org/browse/mutter/commit/?id=4752d427e4e5d1fdbc306134bc4b47e671a24b17 which is in 3.11.5 and in the 3.10 branch (no release yet).
drago01: I'm still seeing this crash in F20 even though it uses mutter 3.10.4 which contains the patch you mentioned (with commit id 24f5b37d) so it looks like this patch alone is not enough.
I'm seeing this crash on F21 (Rawhide), with mutter mutter-3.12.0-2.fc21.x86_64.
Another user experienced a similar problem:
First time reporting. The problem occured after waking up from suspend and trying to enter my password, gnome shell then froze, displaying one of my windows(rythmbox) and then crashed. I have only one extension, allowing me to hibernate. At the time I had firefox and rythmbox(playing music) open.
reason: gnome-shell killed by SIGSEGV
runlevel: N 5
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.