I usually have the same problem; after entering 'continue' at gdb's prompt, I can recreate the bug but then not ctrl+c back out to gdb's prompt.
I tried it again just now and, although I was unable this time to recreate the 100% CPU bug for some unknown reason, once I added and removed a new keyboard layout twice I got an error from g-s-d and obtained a backtrace (attached). Like I said, I'm not sure if this particular backtrace applies to the bug in question, but it did occur after following the same steps which usually recreate the bug. ** Attachment added: "gdb-gnome-settings-daemon.txt" http://launchpadlibrarian.net/49562738/gdb-gnome-settings-daemon.txt -- Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU https://bugs.launchpad.net/bugs/587228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
