This is unlikely as the glibc bug is a very recent one.
--
[Hardy] Tracker does not respond to DBUS
https://bugs.launchpad.net/bugs/190918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I believe my problem here was with Bug #201673. Tracker was probably one
of the affected applications before I turned off my computer and
couldn't get it to start up again.
** Changed in: tracker (Ubuntu)
Status: New = Invalid
--
[Hardy] Tracker does not respond to DBUS
I know it's recent. It went away for some time already, then came back
last night after the glibc update.
--
[Hardy] Tracker does not respond to DBUS
https://bugs.launchpad.net/bugs/190918
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
I wonder whether it would make sense to not autostart trackerd via DBus;
either it's running because it was started with the session or it's not;
it should get autoactivated if it isn't running.
Alternatively, gtk+ could avoid starting it if the DBus service isn't
present.
--
[Hardy] Tracker
It is autoactivated at the moment, but it still refuses to respond to DBUS
requests. Does that make sense? It's as if it's doing its own thing and not
responding to DBUS even if it's not indexing. And it definitely should not
be indexing considering I've turned it off in tracker-preferences.
On
