I did the file rename in #33, logged out and back in again and restored the keyboard.gnome-settings-plugin filename and the problem did not come back. I went to my browser history and reloaded all the pages at the time the keyboard error kicked in and none of them set off the num lock error. So I'm ast least guilty of attributing cause to correlation.
on the up side, restoring the keyboard file, which appears to be just a list of languages in their own scripts to indicate keyboard layouts, did not cause the numlock problem to recur, so maybe folks who need that file can safely restore it after deleting and logging out and in. gnome settings daemon is happily sleeping at 0%cpu and numlock is off. Yay. Thank you Mike M for posting the workaround. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/969359 Title: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/969359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
