Comment 11 for bug 85521

Please also note that my above post (providing the backtrace and strace) was a little overzealous -- in my effort to get a useful backtrace (with the built debug-packages) I have been unable to preproduce the described situation since the bugreport, but when I noticed the mentioned 100% CPU activity today I thought that the bug went back -- checked via ps to see if the duplicate gconfd-2 is running and then followed the steps from the wiki to obtain a backtrace of gconfd2. But when I just checked which process has 100% CPU usage it turned out to be... ekiga, NOT gconfd2! But I hope the info was useful after all.