Bug 596764 - [abrt] crash in tracker-0.8.4-1.fc13: raise: Process /usr/libexec/tracker-miner-fs was killed by signal 6 (SIGABRT)
[abrt] crash in tracker-0.8.4-1.fc13: raise: Process /usr/libexec/tracker-min...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: tracker (Show other bugs)
13
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Deji Akingunola
Fedora Extras Quality Assurance
abrt_hash:300f3733d5d89fbcc8ef379481c...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-27 09:24 EDT by Felipe Hommen
Modified: 2010-09-09 14:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-09 14:51:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (8.12 KB, text/plain)
2010-05-27 09:24 EDT, Felipe Hommen
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 620361 None None None Never

  None (edit)
Description Felipe Hommen 2010-05-27 09:24:54 EDT
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/tracker-miner-fs
component: tracker
crash_function: raise
executable: /usr/libexec/tracker-miner-fs
global_uuid: 300f3733d5d89fbcc8ef379481c7bb4530cda8dd
kernel: 2.6.33.4-95.fc13.i686
package: tracker-0.8.4-1.fc13
rating: 4
reason: Process /usr/libexec/tracker-miner-fs was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Felipe Hommen 2010-05-27 09:24:57 EDT
Created attachment 417243 [details]
File: backtrace
Comment 2 Deji Akingunola 2010-09-09 10:02:07 EDT
Do you still have this problem in the latest tracker update?
Comment 3 Felipe Hommen 2010-09-09 14:32:52 EDT
I uninstalled tracker some time ago. Now, I reinstalled it a few hours ago and it seems to work OK. Indexing is completed.

I am using amd64 instead of i686 now.
Comment 4 Deji Akingunola 2010-09-09 14:51:09 EDT
Ok, thanks for the response.

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