Bug 1115230

Summary: [abrt] gnome-shell: _XSend(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: sangu <sangu.fedora>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: fmuellner, jnicol, otaylor, p.malishev, rhbugzilla, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9145c268a12709323e346f9e58ccd69de0a4283f
Whiteboard: abrt_hash:b4f572be821b5a1f02d14e4551494060778e781b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:53:13 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
File: var_log_messages none

Description sangu 2014-07-02 01:43:20 UTC 
Description of problem:
[wayland] Click running applicaion in activities -> gnome-shell crashes

Version-Release number of selected component:
gnome-shell-3.13.3-1.fc21

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell --wayland --display-server
crash_function: _XSend
executable:     /usr/bin/gnome-shell
kernel:         3.15.0-0.rc8.git0.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _XSend at xcb_io.c:460
 #1 _XFlush at xcb_io.c:512
 #2 _XGetRequest at XlibInt.c:1735
 #3 XQueryExtension at QuExt.c:44
 #4 _XiFindEventsSupported at XExtInt.c:171
 #5 XInput_find_display at XExtInt.c:221
 #6 XIUngrabDevice at XIGrabDevice.c:97
 #7 ffi_call_unix64 at ../src/x86/unix64.S:76
 #8 ffi_call at ../src/x86/ffi64.c:525
 #9 gjs_invoke_c_function at gi/function.cpp:949
Comment 1 sangu 2014-07-02 01:43:24 UTC 
Created attachment 913947 [details]
File: backtrace
Comment 2 sangu 2014-07-02 01:43:26 UTC 
Created attachment 913948 [details]
File: cgroup
Comment 3 sangu 2014-07-02 01:43:28 UTC 
Created attachment 913950 [details]
File: core_backtrace
Comment 4 sangu 2014-07-02 01:43:31 UTC 
Created attachment 913951 [details]
File: dso_list
Comment 5 sangu 2014-07-02 01:43:33 UTC 
Created attachment 913952 [details]
File: environ
Comment 6 sangu 2014-07-02 01:43:36 UTC 
Created attachment 913953 [details]
File: exploitable
Comment 7 sangu 2014-07-02 01:43:38 UTC 
Created attachment 913954 [details]
File: limits
Comment 8 sangu 2014-07-02 01:43:40 UTC 
Created attachment 913955 [details]
File: maps
Comment 9 sangu 2014-07-02 01:43:42 UTC 
Created attachment 913956 [details]
File: open_fds
Comment 10 sangu 2014-07-02 01:43:44 UTC 
Created attachment 913957 [details]
File: proc_pid_status
Comment 11 sangu 2014-07-02 01:43:46 UTC 
Created attachment 913958 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 16:05:33 UTC 
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:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 13 Fedora End Of Life 2016-07-19 11:53:13 UTC 
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.