Ubuntu
tracker package

tracker needs to be killed on every boot

Bug #1525628 reported by Danial Behzadi
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Confirmed
Critical
Unassigned

Bug Description

At every boot, tacker-miner-fs and tracker-extract uses all of the processor and needs to be killed manually for computer to work.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: tracker 1.6.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Dec 13 13:02:58 2015
InstallationDate: Installed on 2015-04-24 (232 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: tracker
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Danial Behzadi (dani.behzi) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tracker (Ubuntu):
status: New → Confirmed
Alberto Salvia Novella (es20490446e)
Changed in tracker (Ubuntu):
importance: Undecided → Critical
Zach (zacharyknuth877)
Changed in tracker (Ubuntu):
assignee: nobody → Zach (zacharyknuth877)
dino99 (9d9)
Changed in tracker (Ubuntu):
assignee: Zach (zacharyknuth877) → nobody
Revision history for this message
granjerox (granjerox) wrote :

Had to kill tracker after boot

MyUser@portaildell:~$ apt-cache policy tracker
tracker:
  Installed: 1.6.2-0ubuntu1.1
  Candidate: 1.6.2-0ubuntu1.1
  Version table:
 *** 1.6.2-0ubuntu1.1 500
        500 http://es.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     1.6.2-0ubuntu1 500
        500 http://es.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

MyUser@portaildell:~$ apt-cache madison tracker
   tracker | 1.6.2-0ubuntu1.1 | http://es.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
   tracker | 1.6.2-0ubuntu1.1 | http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
   tracker | 1.6.2-0ubuntu1 | http://es.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

MyUser@portaildell:~$ apt-cache policy tracker
tracker:
  Installed: 1.6.2-0ubuntu1.1
  Candidate: 1.6.2-0ubuntu1.1
  Version table:
 *** 1.6.2-0ubuntu1.1 500
        500 http://es.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     1.6.2-0ubuntu1 500
        500 http://es.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
pagraher@portaildell:~$ apt-cache madison tracker
   tracker | 1.6.2-0ubuntu1.1 | http://es.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
   tracker | 1.6.2-0ubuntu1.1 | http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
   tracker | 1.6.2-0ubuntu1 | http://es.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

Revision history for this message
ChrisOfBristol (chrisofbristol-deactivatedaccount) wrote :

Similar problem, if I stop work it takes over and everything locks up, even though there doesn't appear to be anything to index according to "tracker status". Have had to remove it.

Revision history for this message
Felix Köhler (felix-koehler) wrote :

Just to confirm: this is still very relevant in 2020 :-(

Revision history for this message
Orbatos (orbatos) wrote :

To update: Per the Gnome team this is finally fixed in version 2.3.2, https://gitlab.gnome.org/GNOME/tracker/issues/95

I cannot verify as as this version is not avialable for any current version of Ubuntu, including Focal.

Please update the tracker version in supported channels.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

I see this in high CPU usage after going from Focal (where I did not see it) to Jammy (where it consumes about 2 to 3 cores)

tags: added: jammy
Revision history for this message
ExploreWiki (explorewiki) wrote :

I originally thought I had this problem but it turns out it was nothing to do with tracker.

My problem was with the CPU being throttled to 500Mhz if I turned the power supply on at the wrong time during boot up.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.