Bug 1013346

Summary: [abrt] gnome-shell-3.10.0.1-1.fc20: send_frame_messages_timeout: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Hapoofesgeli
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: amigadave, besser82, dcharlespyle, fiorenzo.desantis, fmuellner, keramidasceid, mclasen, otaylor, samkraju, sanjay.ankur, twaugh, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:cb39cba6dbac2eed517e968340e235adfc75f711
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-17 14:32:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Hapoofesgeli 2013-09-29 12:57:26 UTC 
Version-Release number of selected component:
gnome-shell-3.10.0.1-1.fc20

Additional info:
reporter:       libreport-2.1.7
abrt_installed_version: abrt-2.1.7-1.fc20.x86_64
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: send_frame_messages_timeout
executable:     /usr/bin/gnome-shell
kernel:         3.11.1-300.fc20.x86_64
libreport_version: libreport-2.1.7-1.fc20.x86_64
runlevel:       N 5
satyr_version:  satyr-0.9-1.fc20.x86_64
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 send_frame_messages_timeout at compositor/meta-window-actor.c:938
 #6 meta_run at core/main.c:556

Potential duplicate: bug 1005299
Comment 1 Hapoofesgeli 2013-09-29 12:57:35 UTC 
Created attachment 804676 [details]
File: backtrace
Comment 2 Hapoofesgeli 2013-09-29 12:57:42 UTC 
Created attachment 804677 [details]
File: cgroup
Comment 3 Hapoofesgeli 2013-09-29 12:57:49 UTC 
Created attachment 804678 [details]
File: core_backtrace
Comment 4 Hapoofesgeli 2013-09-29 12:57:56 UTC 
Created attachment 804679 [details]
File: dso_list
Comment 5 Hapoofesgeli 2013-09-29 12:58:02 UTC 
Created attachment 804680 [details]
File: environ
Comment 6 Hapoofesgeli 2013-09-29 12:58:09 UTC 
Created attachment 804681 [details]
File: exploitable
Comment 7 Hapoofesgeli 2013-09-29 12:58:23 UTC 
Created attachment 804682 [details]
File: limits
Comment 8 Hapoofesgeli 2013-09-29 12:58:34 UTC 
Created attachment 804683 [details]
File: maps
Comment 9 Hapoofesgeli 2013-09-29 12:58:40 UTC 
Created attachment 804684 [details]
File: open_fds
Comment 10 Hapoofesgeli 2013-09-29 12:58:47 UTC 
Created attachment 804685 [details]
File: proc_pid_status
Comment 11 Ankur Sinha (FranciscoD) 2013-10-11 02:18:22 UTC 
Just experienced this. Random crash. Didn't do anything special. Has only happened once till now.
Comment 12 D. Charles Pyle 2013-10-17 05:35:52 UTC 
Just happened to me.  Abrt isn't producing a usable backtrace for me, however.
Comment 13 Matthias Clasen 2013-10-17 14:32:10 UTC 

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