I'm seeing the same behaviour on a current jaunty system: In my case gconfd leads to idling at 100% and stopping it reduces activity to about 12%. Killing gconfd-2 does not help, it is respawned immediately.
According to iotop gconfd-2 is continuously writing to the disk with about 40kB/s, and the file ~/.gconfd/saved_state is growing until it's around 1.2MB and then starting again.
I'm seeing the same behaviour on a current jaunty system: In my case gconfd leads to idling at 100% and stopping it reduces activity to about 12%. Killing gconfd-2 does not help, it is respawned immediately.
According to iotop gconfd-2 is continuously writing to the disk with about 40kB/s, and the file ~/.gconfd/ saved_state is growing until it's around 1.2MB and then starting again.