Oops. Now I'm facing a problem which I haven't thought about before and which I
haven't noticed before latest commit.
Zeitgeist-daemon is running with privileges of current user, whilst yum needs
root privileges to run, so yum plugin tries to talk to nonexistent
zeitgeist-daemon in context of root user. As far as I see, this daemon is then
started, however it uses database in /root/.local/share/zeitgeist. I can see
commited events when starting GAJ as root, but not as regular user.
Now, I have no idea what to do with this. Basic possibilities are:
* change zeitgeist-daemon behaviour to make him create his database in a
location which regular user can read and allow daemons running in user-space to
transparently read it and serve it's content to clients,
* make zeitgeist-daemon running as root to proxy all the communication to all
daemons running in contexts of non-root users,
* do the magic and find out somehow who started current sudo or su process and
connect to his zeitgeist-daemon (is it even possible?).
Maybe I should report new bug regarding this situation outside
zeitgeist-dataprovides? I don't know if zeitgeist-daemon guys observe
bugs reported here.
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Data-Sources.
Add support for yum
Status in Zeitgeist Data-Providers:
I'm not sure if adding this to Zeitgeist makes sense, but sometimes I would
like to see what package (and when) I've installed without opening PackageKit
and browsing logs.
If Zeitgeist Data-Providers team also would like this in Zeitgeist, I'm
willing to write a plugin.
Mailing list: https://launchpad.net/~zeitgeist
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp