Bug 599278 - [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)
Summary: [abrt] crash in abrt-gui-1.1.1-1.fc13: IA__gtk_text_mark_get_buffer: Process ...
Keywords:
Status: CLOSED DUPLICATE of bug 596592
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d297bfeffc45793a57054dc7667...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-03 02:08 UTC by David M.
Modified: 2010-11-08 20:03 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 20:03:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (20.65 KB, text/plain)
2010-06-03 02:08 UTC, David M.
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.