abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/tracker-extract component: tracker crash_function: gst_pnmdec_chain_ascii executable: /usr/libexec/tracker-extract global_uuid: ba2611ece9d9fb49004c3063e216cb826b865d2b kernel: 2.6.33.5-112.fc13.x86_64 package: tracker-0.8.4-1.fc13 rating: 4 reason: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- After 30 minutes or so of attempting to index my home directory, tracker reliably segfaults.
Created attachment 423855 [details] File: backtrace
Package: tracker-0.8.4-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Occured during index of home directory
Package: tracker-0.8.4-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Triggered during initial index of home directory
Package: tracker-0.8.4-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Initial home directory index
Package: tracker-0.8.4-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Initial indexing
Package: tracker-0.8.4-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Occured during initial indexing
Package: tracker-0.8.4-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Initial index
This seems to be a bug in gstreamer; can you please provide the file it is crashing on?
Can you let me know how to identify which file it's running on at the time?
(In reply to comment #10) > Can you let me know how to identify which file it's running on at the time? It usually can be found in ~/.local/share/tracker/tracker-extract.log. Moreover the file is information is included in the backtrace you attached with the bug, 'file:///home/mjg59/Source/ubuntu-lucid/drivers/video/logo/logo_m32r_clut224.ppm'.
It seems clear to me that the crash is really in gstreamer, re-assigning.
Created attachment 424215 [details] Crashing file Ok, here's a file that triggers it.
Yeah, I looked at the backtrace to find the file. Seems GStreamer's pnm decoder is not what you would consider production-quality. Anybody has an idea why Tracker tries to use GStreamer for PNM files? FWIW, I fixed it upstream in http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/commit/?id=147e0682b48d1be4ce0f3b9f6562798f74ecf426
*** Bug 604507 has been marked as a duplicate of this bug. ***
*** Bug 604998 has been marked as a duplicate of this bug. ***
*** Bug 608995 has been marked as a duplicate of this bug. ***
*** Bug 612044 has been marked as a duplicate of this bug. ***
*** Bug 619943 has been marked as a duplicate of this bug. ***
*** Bug 627502 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.