Description of problem: After connecting through GDM, gnome session loading hangs after a few seconds without any message nor warning (nothing in /var/log/messages either). Version-Release number of selected component (if applicable): (Fresh install of) Fedora 9 updated with the latest packages How reproducible: 99% of the time (I managed to connect maybe once or twice maybe) Steps to Reproduce: 1.Connect with GDM 2.Wait and wait, ... Additional info: I tried to trace back the problem and it seems the only way to workaround is to kill gnome-setting-daemon which is not always possible since alt+f1 ends up hanging the whole system if it isn't done BEFORE gnome-setting-daemon hangs. The only way I can see GNOME "fully" (except gnome-setting-daemon) loaded is, before connecting with GDM, go to a console, connect, run top; then connect to GDM, quickly go back to the console and wait for the hang to happen, then kill the daemon. It seems that the hang happens just after pulseaudio is started and I had strange things happening with pulseaudio like the starting/welcoming sound was crippled when GDM would start. I tried to set enable_esd/sound_events keys in global system configuration to false (which resulted to false for me) but gnome-setting-daemon still starts pulseaudio. I also disabled sound module for GDM but no more luck. I'd be happy to help fix this issue by providing whatever information you need.
Could you please gather a backtrace of the hang? Follow the instructions at: http://fedoraproject.org/wiki/StackTraces to install the debuginfo packages. Follow the normal instructions in gdb, but use: gdb attach `pidof gnome-settings-daemon` to launch gdb (this should attach to the running instance of gnome-settings-daemon, type "continue" to make continue running the application).
Created attachment 314464 [details] Backtrace after gnome-settings-daemon locks up
Here is the backtrace (hard to get, I had to use top to kill daemon on one console and gdb on another). The problem seems to be indeed related to audio ... Anyway, I also kept a core file in case you want it too.
Your name came up in the brasero discussion and it reminded me that this bug has been fixed by whatever upgrade I did recently (for quite some time).