Bug 622031 - [abrt] crash in gedit-1:2.30.2-1.fc13: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
[abrt] crash in gedit-1:2.30.2-1.fc13: Process /usr/bin/gedit was killed by s...
Status: CLOSED DUPLICATE of bug 627772
Product: Fedora
Classification: Fedora
Component: gedit (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-06 15:56 EDT by Daniel VanStone
Modified: 2010-11-09 11:33 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 11:33:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (34.02 KB, text/plain)
2010-08-06 15:56 EDT, Daniel VanStone
no flags Details

  None (edit)
Description Daniel VanStone 2010-08-06 15:56:29 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gedit '/home/daniel/.sand-box/google_appengine/templates/Viewing Paste #45034.html'
component: gedit
crash_function: _gtk_text_btree_get_chars_changed_stamp
executable: /usr/bin/gedit
global_uuid: d60306fb180861e0ac645bf5b96e0f01cbcbb7a7
package: gedit-1:2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Saved a fpaste I put up with 
browser saved from google chrome 
opened with gedit
attempted to edit and gedit crashed
at first edit

How to reproduce
1.opened a document and attempted to edit gedit crashed
Comment 1 Daniel VanStone 2010-08-06 15:56:31 EDT
Created attachment 437250 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 11:33:32 EST

*** This bug has been marked as a duplicate of bug 627772 ***
Comment 3 Karel Klíč 2010-11-09 11:33:32 EST
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 #627772.

Sorry for the inconvenience.

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