*Note*: the below is copy & paste from https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1395547 as per request by Thaddaeus Tintenfisch (thad-fisch) on 2014-12-13. Let me know if I should copy other things from there or if having a reference to that is enough / acceptable. Just upgraded to Xubuntu 14.10, had issues with fglrx (see http://askubuntu.com/questions/552795/xubuntu-14-10-upgrade-issues-with-fglrx), went back to radeon drivers. Now it looks to be OK, however after locking the screen using xflock4 and unlocking, I get these three processes using a lot of CPU (this is on 4-core Phenom II X4 N950): PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1572 root 20 0 262892 56672 26480 R 89.7 1.4 6:48.70 Xorg 5025 usr 20 0 312116 11336 4632 R 36.9 0.3 0:17.42 xfce4-volumed 5036 usr 20 0 327328 10556 5760 S 31.5 0.3 0:13.38 xfsettingsd Additional information: - Killing and restarting xfsettingsd and xfce4-volumed resolves the issue until next sleep cycle - When running only xfce4-volumed, but not xfsettingsd, the issue does not appear - This can be reproduced always. ATI Radeon Mobility HD 5650 video card - The CPU usage does not seem to go down after a while - If I got it correctly, it looks like some other processes are also going to high CPU usage after killing xfce4-volumed. I think I saw xfce4-xkb-plugin going to 95% CPU usage - The issue happens before unlock, i.e. locking then pressing a key to get a login dialog, then switching to vty1 and doing a top yields the above Not sure what else I should check / post that can be useful for troubleshooting, let me know. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xfce4-settings 4.11.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 23 18:34:02 2014 InstallationDate: Installed on 2014-04-24 (213 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xfce4-settings UpgradeStatus: Upgraded to utopic on 2014-11-22 (0 days ago)
I have the same issue but with intel graphics. One difference is that that the high load on Xorg goes away after about a minute and the system behaves normally. I can also produce this high load using xmodmap -pke > .Xmodmap xmodmap ~/.Xmodmap
*** Bug 11611 has been marked as a duplicate of this bug. ***
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: xmodmap -pke > .Xmodmap xmodmap ~/.Xmodmap and I can confirm it generates high load on my machine, too. In my case, it took 4 minutes for this one also to calm down, which is somewhat consistent with the 3 minutes I measured before when unlocking the screen.
Thanks for your comment! Do you have a workaround on your system? Next thing I was going to try is to experiment with different tools to provide screen locking (light-locker, xscreensaver, gnome-screensaver, ...).
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 interaction with the X system. Check my comment #3 on the referenced launchpad bug (https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1395547/comments/3), where I outline that when I kill xfsettingsd, lock, unlock, I don't see the CPU issue. Given comment #8 on that bug (https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1395547/comments/8), it might be that it's related to libkeybinder + layout changes, which might be triggered by the xmodmap commands you can reproduce the bug with. I put as much information on the other bug report as I knew how to gather / thought would be useful. If somebody can let me know what could help fixing, I can try providing those or doing additional testing.
Okay, I found a great workaround for me: 1. I made sure I removed light-locker, gnome-screensaver, xscreensaver, kscreensaver, etc.. 2. installed xscreensaver 3. reboot Standby/resume and screen unlocking now works perfectly. While xmodmap is still broken, I don't care about that.
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!
Closing old bugreports