[Ubuntu-x-swat] [Bug 1395547]

Unfortunately, nothing better than just: killall xfsettingsd; killall xfce4-volumed; sleep 6; xfsettingsd & xfce4-volumed & I don't think it is a problem with the locker itself though, to me it looks like it's just a trigger for an issue in xfce4-volumed or something related to its interactio

[Ubuntu-x-swat] [Bug 1395547]

Thanks Timo - I only had light-locker installed, so I did this: 1. Uninstall light-locker 2. Install xcreensaver 3. Reboot Agreed, it seems to be working fine now, so might be something related either to light-locker or how it interacts with xfsettingsd. Thanks for posting a workaround! -- You

[Ubuntu-x-swat] [Bug 1395547]

Thanks Timo. Check the comment #7 I posted on the launchpad bug - (https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1395547/comments/7). It actually goes down for me too, though it takes a bit longer, 3 minutes on my particular machine. I tried the thing you used to reproduce: xm

[Ubuntu-x-swat] [Bug 1395547] Re: xfsettingsd and xfce4-volumed using a lot of CPU after screen lock / unlock

As per request by Thaddaeus Tintenfisch (thad-fisch) on 2014-12-13:, I've created a bug report on bugzilla.xfce.org: https://bugzilla.xfce.org/show_bug.cgi?id=11497 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu.

[Ubuntu-x-swat] [Bug 1395547] Re: xfsettingsd and xfce4-volumed using a lot of CPU after screen lock / unlock

I ran a strace on the xfsettingsd pid, logged out, logged in and I could see a lot of these repeating: poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3, revents=POLLOUT}]) writev(3, [{"\20\0\3\0\3\0\0\0AltL", 12}, {NULL, 0}, {"", 0}], 3) = 12 poll([{fd=3, events=POLLIN}], 1, 42949