Bug 193214

I see the same symptom. CPU usage is in the 90% plus range.

What happens is that the screen comes up for configuration. You are not able to
select any tab on the GUI interface. Killing the application does not stop the
complete program. The only way to kill the process is ctl-C from the terminal
that gdmsetup is launched from.

I do not know how to properly use strace but was able to get this looped output.
See attached file.

(In reply to comment #1)
> I see the same symptom. CPU usage is in the 90% plus range.
> 
> What happens is that the screen comes up for configuration. You are not able to
> select any tab on the GUI interface. Killing the application does not stop the
> complete program. The only way to kill the process is ctl-C from the terminal
> that gdmsetup is launched from.
> 
> I do not know how to properly use strace but was able to get this looped output.
> See attached file.
Where is an attached file?

gdmsetup in gdm-2.15.3-8 continues to be broken in this way and unusable.

Created attachment 130948 [details]
What attachment?

The attachment that I did not attach from strace previously.
sorry for oversight.

This problem is still present in FC6 test 1.

https://www.redhat.com/archives/fedora-test-list/2006-June/msg00380.html

This problem is still present in FC6 test 1.

Correction:
https://www.redhat.com/archives/fedora-test-list/2006-June/msg00372.html

These problems also apply to my FC6-T1 gdmsetup.  Force Quit is the only option
from the gui.  

As mentioned in 196653, which appears to be the same problem, here's some lines
from /var/log/messages that pertain:

Jun 28 20:40:47 localhost gconfd (root-3553): starting (version 2.14.0), pid
3553 user 'root'
Jun 28 20:40:47 localhost gconfd (root-3553): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration sou
rce at position 0
Jun 28 20:40:47 localhost gconfd (root-3553): Resolved address
"xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jun 28 20:40:47 localhost gconfd (root-3553): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration sour
ce at position 2
Jun 28 20:41:47 localhost gconfd (root-3553): GConf server is not in use,
shutting down.
Jun 28 20:41:47 localhost gconfd (root-3553): Exiting
Jun 28 20:41:51 localhost gconfd (root-3940): starting (version 2.14.0), pid
3940 user 'root'
Jun 28 20:41:51 localhost gconfd (root-3940): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration sou
rce at position 0
Jun 28 20:41:51 localhost gconfd (root-3940): Resolved address
"xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jun 28 20:41:51 localhost gconfd (root-3940): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration sour
ce at position 2

I am seeing the same problem - I can click on a the window or a tab in gdmsetup
for half a second, then it freezes and eats 100% of my CPU cycles.
Firewing1

*** Bug 196653 has been marked as a duplicate of this bug. ***

Error still present in gdm-2.15.6-1.

Someone mentioned gdmsetup not consuming so much cpu usage. The message was
correct. It is possible to configure gdmsetup with gdm-2.15.6-3
Tested and configured with success.

Yes and I can confirm, that this is finally fixed in 2.15.6-3 from rawhide. 
Someone might want to close it if a few others also confirm.

Works for me too.

Checking the changelog, it was the purpose of the update.

* Fri Jul 14 2006 Ray Strode <rstrode> - 1:2.15.6-3
- fix hang in gdmsetup

Thanks Ray!

Thanks for confirming the fix worked guys.