Bug 599278

Summary: [abrt] crash in abrt-gui-1.1.1-1.fc13: IA__gtk_text_mark_get_buffer: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David M. <skaturn>
Component: gtk2Assignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: anton, dvlasenk, iprikryl, jmoskovc, kklic, mclasen, mnowak, npajkovs
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:d297bfeffc45793a57054dc7667b170e25a5e837
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 20:03:09 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 David M. 2010-06-03 02:08:32 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/share/abrt/CCMainWindow.py
component: abrt
crash_function: IA__gtk_text_mark_get_buffer
executable: /usr/bin/python
global_uuid: d297bfeffc45793a57054dc7667b170e25a5e837
kernel: 2.6.33.5-112.fc13.i686.debug
package: abrt-gui-1.1.1-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Start bug report generation sequenct.
2. Highlight all debugging output in window (Using mouse left click) and scroll to top of window while ABRT attempts to close said window.
3. ABRT Fails.
3.
Comment 1 David M. 2010-06-03 02:08:34 UTC 
Created attachment 419231 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 20:03:09 UTC 

*** This bug has been marked as a duplicate of bug 596592 ***
Comment 3 Karel Klíč 2010-11-08 20:03:09 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #596592.

Sorry for the inconvenience.