Tracker uses 100% cpu on clean install and doing some basic things
Naguam PostOwl
maugbis at gmail.com
Tue Aug 3 18:11:58 BST 2021
Hello,
I didn't really understand how the debian bug report system works.
So I decided to send an email to the maintainers of the package.
I think it's important tell you about this bug because of the imminent
release of debian 11.
Please read until the end, I will talk about building a kernel but it's the
way i reproduced the bug.
So here is the report :
Package : tracker
Version : 2.3.6-2
I made a clean install of debian gnome bullseye with the rc3 installer (and
installed firmwares etc) on my x260 laptop.
Then builded an upstream kernel and seeing a 100% cpu usage (event after
the build) from tracker miner fs.
Here is how to reproduce the bug
Then opened a terminal to execute
$ sudo apt build-dep linux
To install the dependencies to build a newer kernel.
Then I downloaded the 5.13.7 kernel archive on kernel.org.
I checked the signatures and checksum etc...
Then I 'untared' the archive and went into it using.
$ tar xaf linux-5.13.7.tar.xz && cd linux-5.13.7
I made the configuration I wanted (took my other laptop fedora 34 linux
5.13.5 configuration)
$ make oldconfig
Then
$ make deb-pkg -j 4 *# + options for version
naming that are not important *
* # because it
builds and it's not a problem about building *
*# the
kernel.*
Then watch htop and see the tracker-miner (or tracker-extract) process
using many cpu.
I don't now if that problem started when I 'untared' or if it was after
starting the build.
At least after the build it took a really long time to finish.
Thank you for your attention.
I'm pleased to try to contribute to debian.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20210803/dd991760/attachment.htm>
More information about the pkg-gnome-maintainers
mailing list