After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 701468 - Has setting to not index on battery, ignores it
Has setting to not index on battery, ignores it
Status: RESOLVED DUPLICATE of bug 703759
Product: tracker
Classification: Core
Component: Miners
0.16.x
Other Linux
: Normal normal
: ---
Assigned To: tracker-general
Depends on:
Blocks:
 
 
Reported: 2013-06-02 17:16 UTC by Andreas Kloeckner
Modified: 2013-07-31 22:34 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Software versions as reported by Debian (1.50 KB, application/octet-stream)
2013-06-02 17:16 UTC, Andreas Kloeckner 		Details
Screenshot of prefs dialog (52.03 KB, image/png)
2013-06-03 13:19 UTC, Andreas Kloeckner 		Details

Description Andreas Kloeckner 2013-06-02 17:16:54 UTC 
Created attachment 245866 [details]
Software versions as reported by Debian

I like that tracker has a setting for not starting the miner while on battery. I don't like that it appears to ignore that setting. Every time I turn on my laptop while on battery, there's a process called 'tracker-miner-fs' at 100% CPU (much of that IOWait). This process also does not respond to SIGTERM, only SIGKILL finishes it off.
Comment 1 Andreas Kloeckner 2013-06-02 17:19:46 UTC 
I misremembered--the busy process is 'tracker-store'.
Comment 2 Martyn Russell 2013-06-03 08:18:08 UTC 
Hello Andreas,

Do you know if this was the first index of your system? There is another option there which circumvents the regular preference you talk about. In the tracker-preferences, it is titled "Enable for initial data population". Is that checked/enabled?

Thanks,
Comment 3 Andreas Kloeckner 2013-06-03 13:19:27 UTC 
Created attachment 245921 [details]
Screenshot of prefs dialog

Not as far as I know. Screenshot of prefs dialog attached.
Comment 4 Martyn Russell 2013-07-31 22:34:37 UTC 
Hello Andreas, I think it's fixed in 0.16.2 which I just released. Any chance you can test with that and let me know how you get on?

Thanks... For details, see bug 703759.

I am going to mark this as fixed for now, if this is still an issue, please reopen. Thanks again for reporting :)

*** This bug has been marked as a duplicate of bug 703759 ***