Comment 20 for bug 293535

Backup the ~/.gconf folder or simply rename it to .gconf_old and relogin. A new .gconf will be created with some default settings.

Then move the one of folders from gconf_old to the new gconf and relogin to see until you get that high-cpu usage again. Thus you will have singled out the problem.

For me, the problematic setting was ~/.gconf/desktop/gnome/remote_access. I didnt include this folder in my new settings and now everything is fine.

I had to login/logout several times though in order to spot the culprit... Hope this helps...