Bug 613225 - [abrt] crash in gedit-1:2.28.3-1.fc12: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gedit-1:2.28.3-1.fc12: Process /usr/bin/gedit was killed by s...
Status: CLOSED DUPLICATE of bug 549940
Alias: None
Product: Fedora
Classification: Fedora
Component: gedit
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:2f3ced7569c78e979679fed3041...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-10 05:36 UTC by Vector Thorn
Modified: 2010-11-08 18:50 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2010-11-08 18:50:23 UTC

Attachments (Terms of Use)
File: backtrace (34.79 KB, text/plain)
2010-07-10 05:37 UTC, Vector Thorn
no flags Details

Description Vector Thorn 2010-07-10 05:36:59 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gedit
comment: Gedit does NOT like database dumps where records are NOT separated on a new line for each record. For example, if you have 100 insert statements all on the same line, as is the default output for most database tools, then gedit will show some strange behaviors, such as overlapping text, no h-scroll bar, etc. You can do a search and replace to fix this, by searching for ),( and replacing it with ),\n( but gedit does not like doing this either. Use sed to do this as you dump the database that way it is already formatted in a way that does not cause gedit to go into epileptic shock.
component: gedit
crash_function: _gtk_text_btree_get_chars_changed_stamp
executable: /usr/bin/gedit
global_uuid: 2f3ced7569c78e979679fed30410b59977adc7b0
package: gedit-1:2.28.3-1.fc12
rating: 4
reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. Delete a large block of text from a database dump
2. crash
3. repeat steps 1 and 2

Comment 1 Vector Thorn 2010-07-10 05:37:01 UTC
Created attachment 430827 [details]
File: backtrace

Comment 2 Bug Zapper 2010-11-03 12:10:16 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 3 Karel Klíč 2010-11-08 18:50:23 UTC

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

Comment 4 Karel Klíč 2010-11-08 18:50:23 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 #549940.

Sorry for the inconvenience.

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