Bug 690594

Summary: [abrt] gnome-utils-1:2.91.91-1.fc15: gdict_sidebar_current_page: Process /usr/bin/gnome-dictionary was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Troy <troyatlarge>
Component: gnome-utilsAssignee: 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:56c74ef032e22e722682788da0e7fe2678aa6acf
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-15 05:47:09 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 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 ***