Bug 690594 - [abrt] gnome-utils-1:2.91.91-1.fc15: gdict_sidebar_current_page: Process /usr/bin/gnome-dictionary was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-utils-1:2.91.91-1.fc15: gdict_sidebar_current_page: Process /usr...
Keywords:
Status: CLOSED DUPLICATE of bug 681745
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-utils
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:56c74ef032e22e722682788da0e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-24 18:19 UTC by Troy
Modified: 2011-04-15 05:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-15 05:47:09 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (16.57 KB, text/plain)
2011-03-24 18:19 UTC, Troy
no flags Details

Description Troy 2011-03-24 18:19:19 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 16972 bytes
cmdline: gnome-dictionary
comment: I updated Fedora 15 Alpha this morning, then went into using it trying various programs for errors, of which gnome-dictonary was one. Opened it, searched for the word "syzygy", it gave the defintion, then closed it.
component: gnome-utils
Attached file: coredump, 20635648 bytes
crash_function: gdict_sidebar_current_page
executable: /usr/bin/gnome-dictionary
kernel: 2.6.38-1.fc15.i686.PAE
package: gnome-utils-1:2.91.91-1.fc15
rating: 4
reason: Process /usr/bin/gnome-dictionary was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1300973314
uid: 500

How to reproduce
-----
1.
2.
3.
I opened gnome-dictionary, looked up a word and then closed it - was not aware of any problem until the bug report came up.

Comment 1 Troy 2011-03-24 18:19:21 UTC
Created attachment 487404 [details]
File: backtrace

Comment 2 Matthias Clasen 2011-04-15 05:47:09 UTC

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


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