Bug 681583

Summary: [abrt] gedit-2:2.91.7-1.fc15: settings_backend_path_changed: Process /usr/bin/gedit was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Adam Plumb <adamplumb>
Component: geditAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: mclasen, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:57f59a2c32f4661da3818e8c78975d32a9edc71d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-08 00:42:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Adam Plumb 2011-03-02 16:28:01 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 16613 bytes
cmdline: gedit
comment: This has happened to me several times at random.  There doesn't seem to be any particular pattern, though it might be when I'm opening/closing files.
component: gedit
Attached file: coredump, 43311104 bytes
crash_function: settings_backend_path_changed
executable: /usr/bin/gedit
kernel: 2.6.38-0.rc6.git6.1.fc15.i686
package: gedit-2:2.91.7-1.fc15
rating: 4
reason: Process /usr/bin/gedit was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1299082703
uid: 500

How to reproduce
-----
1. Running Gedit in a normal way, editing files.
2. 
3.
Comment 1 Adam Plumb 2011-03-02 16:28:03 UTC 
Created attachment 481901 [details]
File: backtrace
Comment 2 Matthias Clasen 2011-04-08 00:42:31 UTC 

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