abrt 1.0.0 detected a crash. How to reproduce ----- 1. Start strigiclient 2. Press "start indexing" button 3. Attached file: backtrace cmdline: /usr/bin/strigidaemon component: strigi executable: /usr/bin/strigidaemon kernel: 2.6.31.9-174.fc12.x86_64 package: strigi-0.7.0-1.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 380312 [details] File: backtrace
*** Bug 550488 has been marked as a duplicate of this bug. ***
*** Bug 550489 has been marked as a duplicate of this bug. ***
*** Bug 551124 has been marked as a duplicate of this bug. ***
Does that still happen with 0.7.2-2 for you?
I am running 0.7.2-2 and i think i does happen. Please look at following bug https://bugzilla.redhat.com/show_bug.cgi?id=606121 Is it related?
I'm not 100% sure, but it looks like no. Abrt backtraces aren't easy to read, maybe except for the abrt developers ;) Abrt shouldn't catch strigi crashes in the first place, but that might change in the near future and help us a lot (the way better kde pendant DrKonqi should catch it then). And while i had a second look on the backtrace here, it's as well missing a lot of debuginfo. Stuff like: 0x0000000000000000 in ?? () isn't helpful at all. The only thing i can guess is that it was indexing your mail folders as it crashed. If it crashes next time and you need help with installing debuginfo packages, if possible join the irc channel #fedora-kde on freenode.net. We might be able to help you. That backtrace is sadly not helpful for an upstream bug, but out of curiosity, how much RAM is in your box and how much have you dedicated to strigi/nepomuk?
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.