Bug 690140 - [abrt] gnome-utils-1:2.91.91-1.fc15: Process /usr/bin/gnome-search-tool was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-utils-1:2.91.91-1.fc15: Process /usr/bin/gnome-search-tool was k...
Keywords:
Status: CLOSED DUPLICATE of bug 705480
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-utils
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e38a01ebfaeaebb005167641b56...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-23 12:22 UTC by Lawrence Graves
Modified: 2012-03-30 14:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 14:37:29 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (27.30 KB, text/plain)
2011-03-23 12:22 UTC, Lawrence Graves 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Lawrence Graves 2011-03-23 12:22:57 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 27954 bytes
cmdline: gnome-search-tool
component: gnome-utils
Attached file: coredump, 59584512 bytes
executable: /usr/bin/gnome-search-tool
kernel: 2.6.38-1.fc15.x86_64
package: gnome-utils-1:2.91.91-1.fc15
rating: 4
reason: Process /usr/bin/gnome-search-tool was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1300882616
uid: 500

How to reproduce
-----
1.I don't have a clue as to when this occurred. After the last update.
2.
3.
Comment 1 Lawrence Graves 2011-03-23 12:22:59 UTC 
Created attachment 487021 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 14:37:29 UTC 
Backtrace analysis found this bug to be similar to bug #705480, closing as duplicate.

Bugs which were found to be similar to this bug: bug #692718, bug #698036, bug #701004, bug #705480

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 705480 ***
Note You need to log in before you can comment on or make changes to this bug.