Ubuntu
gconf package

  1. Bug #293535
  2. Comment #30

Comment 30 for bug 293535

Revision history for this message
Darxus (darxus) wrote :

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.