Bug 623983 - [abrt] crash in strigi-0.7.2-5.fc13: Process /usr/bin/strigidaemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in strigi-0.7.2-5.fc13: Process /usr/bin/strigidaemon was killed...
Keywords:
Status: CLOSED DUPLICATE of bug 630380
Alias: None
Product: Fedora
Classification: Fedora
Component: strigi
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7d05e4b639490ee289bee8f4636...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-13 10:54 UTC by Patrick C. F. Ernzer
Modified: 2010-11-08 17:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 17:33:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (21.82 KB, text/plain)
2010-08-13 10:54 UTC, Patrick C. F. Ernzer 		no flags Details
View All

Description Patrick C. F. Ernzer 2010-08-13 10:54:15 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/strigidaemon
comment: close if no useful info in backtrace
component: strigi
crash_function: ClientInterface::getIndexedFiles
executable: /usr/bin/strigidaemon
global_uuid: 7d05e4b639490ee289bee8f4636561b0db9bd1bf
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: strigi-0.7.2-5.fc13
rating: 4
reason: Process /usr/bin/strigidaemon was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: 1. unsure, I switched on gnome shell and saw this in ABRT a while later
Comment 1 Patrick C. F. Ernzer 2010-08-13 10:54:18 UTC 
Created attachment 438650 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 17:33:03 UTC 

*** This bug has been marked as a duplicate of bug 630380 ***
Comment 3 Karel Klíč 2010-11-08 17:33:03 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #630380.

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