Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40555 - [tracker] tracker-store uses 100% CPU

Attached to Project: Arch Linux
Opened by Marc Rechté (mrechte) - Monday, 26 May 2014, 09:14 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 06 July 2015, 04:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Since recently I noticed tracker-store eats 100% of 1 CPU core.
tracker-control -S shows no progress in the indexing.
Issuing tracker-control -t actually terminates the tracker-store process.
May be not an Arch specific issue
Thanks

Additional info:
* package version(s)
tracker 1.0.1-1

* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 06 July 2015, 04:37 GMT
Reason for closing:  No response
Comment by Jan Alexander Steffens (heftig) - Tuesday, 27 May 2014, 09:44 GMT
I have seen this as well. Hasn't happened since hard-resetting tracker using tracker-control -r
Comment by Marc Rechté (mrechte) - Thursday, 16 October 2014, 06:32 GMT
Problem is still here. Store process does not even respond to a kill (except -9).

To permanently remove this component: # pacman -R tracker gnome-documents gnome-online-miners
Comment by Jan Alexander Steffens (heftig) - Thursday, 16 October 2014, 06:54 GMT
Did you try the hard reset?
Comment by Marc Rechté (mrechte) - Thursday, 16 October 2014, 07:28 GMT
Yes. It is OK until I re-open my Gnome session.
Comment by Doug Newgard (Scimmia) - Friday, 15 May 2015, 03:30 GMT
We've had a number of updates, still an issue?

Loading...