Bug 1010642

Summary: [abrt] gnome-abrt-0.3.1-1.fc19: Process /usr/bin/python2.7 was killed by signal 4 (SIGILL)
Product: [Fedora] Fedora Reporter: mamii <sarrab1976>
Component: gnome-abrtAssignee: Jakub Filak <jfilak>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: jberan, jfilak
Target Milestone: ---Flags: jfilak: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d254f267f474e238291b7efeabc47ac621b5ebad
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-26 06:44:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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 mamii 2013-09-22 08:53:45 UTC 
Version-Release number of selected component:
gnome-abrt-0.3.1-1.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/gnome-abrt
executable:     /usr/bin/python2.7
kernel:         3.11.1-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 ??
 #2 XGetWindowProperty at GetProp.c:69
 #3 gdk_x11_window_get_frame_extents at gdkwindow-x11.c:3027
 #4 Oxygen::Gtk::gdk_toplevel_get_frame_size at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygengtkutils.cpp:890
 #5 Oxygen::Gtk::gdk_window_map_to_toplevel at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygengtkutils.cpp:747
 #6 gdk_map_to_toplevel at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygengtkutils.h:117
 #7 Oxygen::Style::renderWindowBackground at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenstyle.cpp:288
 #8 Oxygen::Style::renderHoleBackground at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenstyle.cpp:792
 #9 Oxygen::InnerShadowData::targetExposeEvent at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenstyle.h:181
 #10 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
Comment 1 mamii 2013-09-22 08:53:49 UTC 
Created attachment 801139 [details]
File: backtrace
Comment 2 mamii 2013-09-22 08:53:52 UTC 
Created attachment 801140 [details]
File: cgroup
Comment 3 mamii 2013-09-22 08:53:56 UTC 
Created attachment 801141 [details]
File: core_backtrace
Comment 4 mamii 2013-09-22 08:53:59 UTC 
Created attachment 801142 [details]
File: dso_list
Comment 5 mamii 2013-09-22 08:54:01 UTC 
Created attachment 801143 [details]
File: environ
Comment 6 mamii 2013-09-22 08:54:04 UTC 
Created attachment 801144 [details]
File: exploitable
Comment 7 mamii 2013-09-22 08:54:07 UTC 
Created attachment 801145 [details]
File: limits
Comment 8 mamii 2013-09-22 08:54:11 UTC 
Created attachment 801146 [details]
File: maps
Comment 9 mamii 2013-09-22 08:54:14 UTC 
Created attachment 801147 [details]
File: open_fds
Comment 10 mamii 2013-09-22 08:54:18 UTC 
Created attachment 801148 [details]
File: proc_pid_status
Comment 11 mamii 2013-09-22 08:54:21 UTC 
Created attachment 801149 [details]
File: var_log_messages
Comment 12 Jakub Filak 2013-09-23 08:19:36 UTC 
Thank you for the bug report. This seems more like a bug in oxygen-gtk or gtk3. Unfortunately, we need to know how this happened. If you have time and can still reproduce the bug, please provide a textual description or better a demonstrative video [1].


1: https://fedoraproject.org/wiki/Bugs_and_feature_requests?rd=BugsAndFeatureRequests#Graphical_User_Interfaces
Comment 13 Jakub Filak 2014-11-26 06:44:26 UTC 
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. 

Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.