On Thu, 14 Feb 2013 18:35:23 +0100, Hans de Goede wrote:
On Thu, 14 Feb 2013 03:49:23 +0100, Kevin Kofler wrote:
DJ Delorie wrote:
Disadvantage, if you ask me. First thing audacious did was spew random errors to the screen and change my Firefox and emacs cursors.
So I suspect that Audacious started gnome-settings-daemon.
It doesn't do that when I use OpenBox instead of GNOME, so OpenBox does not auto-spawn g-s-d.
However, one of its plug-ins talks to DBus (org.gnome.SettingsDaemon) for GNOME media player keyboard shortcuts. That plug-in is enabled by default and by request, and anyone not running a compatible environment can easily switch it off in the preferences.
Or you could fix the plugin to not auto-start the daemon so we don't get blamed for Audacious bugs...
Actually after seeing this thread I was planning on sending a mail to ask people how to fix this. I guess that dbus-activation causes g-s-d to start when the audacious tries to talk to it.
Rather then a less the friendly worded reply, it would be actually helpful if you could tell us (pointer to a code example would be a bonus) how to talk to a dbus interface without causing dbus-activation to trigger.
What I checked in ~13 hours ago is this:
http://pkgs.fedoraproject.org/cgit/audacious-plugins.git/commit/?id=55972c07...
Reviews/feedback appreciated. Preferably, I'd still like to see a test-case where g-s-d would be started automatically. Chasing ghosts is not so funny.