Bug 626228

Summary: [abrt] yumex-2.9.10-1.fc13: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Stefan Gies <stefan998>
Component: 0xFFFFAssignee: Tim Lauridsen <tim.lauridsen>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: dwmw2, kenmatrix, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:2c22b5588c6775b5f2dedb6e2eebf440063e70e1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-02 09:50:49 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

Description Stefan Gies 2010-08-22 21:09:45 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/share/yumex/yumex.pyc
component: yumex
crash_function: raise
executable: /usr/bin/python
kernel: 2.6.33.6-147.2.4.fc13.i686.PAE
package: yumex-2.9.10-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1282489154
uid: 500

How to reproduce
-----
1.Starting Yumex
2.
3.
Comment 1 Stefan Gies 2010-08-22 21:09:48 UTC 
Created an attachment (id=440258)
File: backtrace
Comment 2 Tim Lauridsen 2011-01-02 09:50:49 UTC 
Some low level gtk or python blows up, can't do anything about that, if you can reproduce, the please reopen.