Comment 7 for bug 1314782

Revision history for this message
Martin Spacek (mspacek) wrote :

Hallelujah! Thanks for the workaround Alistair. I was going somewhat crazy, finding that rather randomly, volume keys and notifications and screen brightness notifications would work, sometimes only one would work, and sometimes neither would work. That smells like some kind of a race condition. This is in Xubuntu 14.04 amd64 on a Thinkpad W510 with nvidia binaries.

At first I thought Bug #1254881 was the problem (xfce session starts multiple instances of xfce4-power-manager and xfce4-volumed), since I had multiple instances of both processes. After going through the procedure in that bug description, I got rid of my multiple instances (and my efforts seem to have stuck after logout and/or reboot), but I still had random functionality of volume keys and brightness notifications. Adding --no-daemon to the Exec line in both xfce4-volumed.desktop and xfce4-power-manager.desktop in /etc/xdg/autostart nailed it. Thanks for the tip!

It seems xfsettingsd also suffers from some kind of DBus communication problem (Bug #1239014, xfsettingsd unable to daemonize properly when overlay scrollbars are activated). I notice that if I try logging out immediately after logging in, the system just sits there for about 10 seconds. I've also been noticing weird behaviour of my workspace applet (wrong workspace labels for the first 10 or 20 sec, which then magically correct themselves to the labels set in the settings), which I suspect might also be related to xfsettingsd. Unfortunately, adding --no-daemon to xfsettingsd.desktop in /etc/xdg/autostart doesn't seem to actually launch xfsettingsd with the --no-daemon flag in the session.

Anyways, any news on merging the fix in the branch so these workarounds aren't required? Has it been tested?