Comment 11 for bug 769948

Sorry I could get back to it so late.

I've figured out a way to handle the problem with root privileges (at least, most cases).
Plugin now forks right after collecting data. Fork tries to find out who ran it really (by checking environment variables) and sets it's UID and GID like he was that user. This one works (I'm able to see events in GAJ as regular user).
Only case when it doesn't work is when yum is being executed with `su -` - whole environment gets replaced - any ideas how to fix it?