Red Hat Bugzilla – Bug 801515
[abrt] tracker-0.13.1-1.fc17: type_get_qdata_L: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
Last modified: 2013-08-01 12:58:27 EDT
libreport version: 2.0.8
reason: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
time: Пт. 09 марта 2012 02:38:17
var_log_messages: Mar 9 02:38:19 saw abrt: Saved core dump of pid 24503 (/usr/libexec/tracker-miner-fs) to /var/spool/abrt/ccpp-2012-03-09-02:38:17-24503 (117760000 bytes)
backtrace: Text file, 71496 bytes
dso_list: Text file, 5507 bytes
maps: Text file, 27218 bytes
smolt_data: Binary file, 2952 bytes
:'IMSETTINGS_MODULE=X compose table'
Created attachment 568703 [details]
Created attachment 568704 [details]
Created attachment 568705 [details]
Created attachment 568706 [details]
tracker-0.14.1-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tracker-0.14.1-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
tracker-0.14.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
The bug is still resurfacing even after the packacge being updated to the mentioned version in resolution. Also the automatic bug tracking is not registering the crash event stating that the package be updated to some new version.
Basically as per my rpm -qi tracker the insatll date of the package is:
[root@mail2 ~]# rpm -qi tracker
Name : tracker
Version : 0.14.1
Release : 1.fc17
Install Date: Sat 02 Jun 2012 01:35:43 PM IST
Whereas I am seeing lots of crashes till today i.e 28 Jun 12 with bug tracker marking the new events as duplicate & not registering the new crash reports.
This is just for your info. It seems there is some problem somewhere or I am understanding the whole situation differently.
please re-open bug
OS Release: Fedora release 17 (Beefy Miracle)
Still broken, but no longer reports to the tracker since it shows as a duplicate. Popped up today during a copy to the machine.
Just occurred with:
Name : tracker
Arch : x86_64
Version : 0.14.4
Release : 1.fc17
Size : 5.1 M
Repo : installed
From repo : updates-testing
Still broken, but no longer reports to the tracker since it shows as a duplicate. Popped up today during another copy to the machine. Can you guide me to any data you may like to have posted?
Still broken, shows as already reported. Just switched over to F18 and came up first day. Can you guide me to any data you may like to have posted?
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.