Is this still an issue now that Zeitgeist has been ported to Vala?
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/772265
Title:
The datahub starts zeitgeist-daemon on
Closing the Zeitgeist task of this since it seems to be a datahub thing.
** Changed in: zeitgeist
Status: New = Invalid
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
I'm adding a libzeitgeist task as well here because it right now
creating either a ZeitgeistLog or ZeitgeistIndex will DBus-activate
zeitgeist-daemon. It's unclear to me what the consequences of not
autostarting zeitgeist from these would be though...
And that said simply twiddling these two
Some reference bedtime reading:
- bug #731019 Certification System 201101-7174 boots 7.93 seconds slower
- http://www.phoronix.com/scan.php?page=articleitem=ubuntu_natty_bootnum=1
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed
I'm not a big friend of the idea to allow someone else than the daemon
itself modify config files like datasources.(pickle|json), because this
would require the daemon to watch-out for changes to all config files it
and its extensions are using.
libzeitgeist and the datahub should instead defer
@Mikkel: Could you check gio's AppLaunched signal? I mean all of this
can be done in vain if any AppLaunched signal is fired during the
session start.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
6 matches
Mail list logo
