Bug 677997 - [abrt] gedit-2:2.91.6-3.fc15: find_root: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
Summary: [abrt] gedit-2:2.91.6-3.fc15: find_root: Process /usr/bin/gedit was killed by...
Keywords:
Status: CLOSED DUPLICATE of bug 676071
Alias: None
Product: Fedora
Classification: Fedora
Component: gedit
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:46bcd1d4ec302d95a388bcb754d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 13:13 UTC by Tim Lauridsen
Modified: 2011-04-14 23:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-14 23:21:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (53.96 KB, text/plain)
2011-02-16 13:13 UTC, Tim Lauridsen
no flags Details

Description Tim Lauridsen 2011-02-16 13:13:35 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 55255 bytes
cmdline: gedit /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.power.gschema.xml
component: gedit
Attached file: coredump, 62734336 bytes
crash_function: find_root
executable: /usr/bin/gedit
kernel: 2.6.38-0.rc4.git7.1.fc15.x86_64
package: gedit-2:2.91.6-3.fc15
rating: 4
reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1297861866
uid: 500

How to reproduce
-----
1. gedit /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.power.gschema.xml
2. click to 'Open' button
3.

Comment 1 Tim Lauridsen 2011-02-16 13:13:37 UTC
Created attachment 479106 [details]
File: backtrace

Comment 2 Tim Lauridsen 2011-02-17 13:51:48 UTC
The crash happen every time I use the 'Open' botton or select File -> Open

gedit somefile from command line works fine.

Comment 3 Matthias Clasen 2011-04-14 23:21:01 UTC

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


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