Bug 593182 - [abrt] crash in gedit-1:2.28.3-1.fc12: raise: Process /usr/bin/gedit was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gedit-1:2.28.3-1.fc12: raise: Process /usr/bin/gedit was kill...
Status: CLOSED DUPLICATE of bug 566780
Alias: None
Product: Fedora
Classification: Fedora
Component: gedit
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:7e130eee18779b84bb8e9f89cb4...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-18 05:21 UTC by Georgi Furnadzhiev
Modified: 2010-05-25 08:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-25 08:39:59 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (16.29 KB, text/plain)
2010-05-18 05:21 UTC, Georgi Furnadzhiev
no flags Details

Description Georgi Furnadzhiev 2010-05-18 05:21:23 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gedit /home/gfurnadzhiev/.cache/.fr-PYITJq/content.xml
component: gedit
crash_function: raise
executable: /usr/bin/gedit
global_uuid: 7e130eee18779b84bb8e9f89cb48082f29df2fbc
package: gedit-1:2.28.3-1.fc12
rating: 4
reason: Process /usr/bin/gedit was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
1. Open ODF file as ZIP archive with GNOME's File Roller
2. Select an XML file to open with gedit
3. Change and save file. Save in the archive too
4. Click gedit's x-button in the top right corner to close the application
5. crash

Comment 1 Georgi Furnadzhiev 2010-05-18 05:21:25 UTC
Created attachment 414732 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 08:39:59 UTC

*** This bug has been marked as a duplicate of bug 566780 ***

Comment 3 Karel Klíč 2010-05-25 08:39:59 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 #566780.

Sorry for the inconvenience.

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