I am also seeing this on Karmic. I also think gconf should not allow another buggy program to use up the CPU. It really needs to throw a user-visible error stating what the problem is, and throttle the other buggy program.
Ah, I believe metacity didn't come up as expected this boot, and I started it from the commandline, so I have two instances. Fighting over gconf? Yup, killing the older instance made the gconf cpu usage go away, and I could see my window manager get reloaded. This is definitely not the way Ubuntu should handle this. -- CPU always 100% CPU https://bugs.launchpad.net/bugs/293535 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
