Same problem here, upgrades Ubuntu 11.10 to 12.04 last week:
- /usr/lib/gnome-settings-daemon/gnome-settings-daemon using 100% CPU after back from screen-saver
- Keyboard "NumLock" blinking very fast
- If kill the gnome-settings-daemon if came back and if screen-saver runs again the bug repeats...
(my keyboard is a Dell Model: SK-8135, don't know if matters)
I also notice something strange, when running "/usr/lib/gnome-settings-daemon/gnome-settings-daemon --debug" manually I can see the output messages, and just by hitting "NunLock" on my keyboard I get the message:
Same message that keeps repeating when the gnome-settings-daemon goes crazy and start consuming 100% CPU.
Workaround?! Maybe, removing the keyboard plugin file from the g-s-d and restarting the daemon:
$ sudo mv /usr/lib/gnome-settings-daemon-3.0/keyboard.gnome-settings-plugin ~/
$ kill <gnome-settings-daemon-PID>
kill it just to re-start the daemon, of if you're running by hand as me, just CTRL+C and start it again.
Well... after that I can lock the screen, let the screen-saver starts, hit "NunLock" on my keyboard and I don't get the error.
I just did that 40 minutes ago, I could be wrong, just get excited to post it because the error message when hitting "NunLock" disappeared.
Hello,
Same problem here, upgrades Ubuntu 11.10 to 12.04 last week: gnome-settings- daemon/ gnome-settings- daemon using 100% CPU after back from screen-saver daemon if came back and if screen-saver runs again the bug repeats...
- /usr/lib/
- Keyboard "NumLock" blinking very fast
- If kill the gnome-settings-
(my keyboard is a Dell Model: SK-8135, don't know if matters)
I also notice something strange, when running "/usr/lib/ gnome-settings- daemon/ gnome-settings- daemon --debug" manually I can see the output messages, and just by hitting "NunLock" on my keyboard I get the message:
"(gnome- settings- daemon: 6711): libappindicator -CRITICAL **: app_indicator_ set_label: assertion `IS_APP_INDICATOR (self)' failed"
Same message that keeps repeating when the gnome-settings- daemon goes crazy and start consuming 100% CPU.
Workaround?! Maybe, removing the keyboard plugin file from the g-s-d and restarting the daemon:
$ sudo mv /usr/lib/ gnome-settings- daemon- 3.0/keyboard. gnome-settings- plugin ~/ settings- daemon- PID>
$ kill <gnome-
kill it just to re-start the daemon, of if you're running by hand as me, just CTRL+C and start it again.
Well... after that I can lock the screen, let the screen-saver starts, hit "NunLock" on my keyboard and I don't get the error.
I just did that 40 minutes ago, I could be wrong, just get excited to post it because the error message when hitting "NunLock" disappeared.
Cheers!