[Bug 458995] Re: [karmic] Trackerd goes into infinite loop indexing .xsession-errors
Jerry Chong
zanglang at gmail.com
Fri Oct 23 11:38:22 UTC 2009
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34245043/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/34245044/XsessionErrors.txt
** Description changed:
Binary package hint: tracker
A few seconds after start indexing, Tracker starts consuming 100% cpu
(or 50% for dual core), and checking .local/share/tracker/trackerd.log
shows that trackerd is stuck in an infinite loop:
23 Oct 2009, 19:27:22: Tracker: Received monitor event:2->'IN_MODIFY' for file:'/home/zanglang/.xsession-errors' (cookie:0)
23 Oct 2009, 19:27:22: Tracker: Received monitor event:2->'IN_MODIFY' for file:'/home/zanglang/.xsession-errors' (cookie:0)
23 Oct 2009, 19:27:22: Tracker: Received monitor event:2->'IN_MODIFY' for file:'/home/zanglang/.xsession-errors' (cookie:0)
23 Oct 2009, 19:27:22: Tracker: Received monitor event:2->'IN_MODIFY' for file:'/home/zanglang/.xsession-errors' (cookie:0)
...
Checking tracker-preferences shows that I indeed had ".xsession-errors"
listed under Ignored File Patterns.
- The bug appears to 100% reproducible everytime I start
- /usr/lib/tracker/trackerd.
+ The bug appears to be 100% reproducible everytime I start trackerd.
I'm not sure if it's related to previous 100% CPU bugs, but Googling
- returns nothing so I assume it's not a duplicate.
+ returns nothing about this .xession-error problem, so I assume it's not
+ a duplicate.
ProblemType: Bug
Architecture: i386
Date: Fri Oct 23 19:27:36 2009
DistroRelease: Ubuntu 9.10
Package: tracker 0.6.95-1ubuntu1
ProcEnviron:
- PATH=(custom, user)
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ PATH=(custom, user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SourcePackage: tracker
Uname: Linux 2.6.31-14-generic i686
--
[karmic] Trackerd goes into infinite loop indexing .xsession-errors
https://bugs.launchpad.net/bugs/458995
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
More information about the universe-bugs
mailing list