Description of problem: I just loaded updates on fedora 11, which included a new gnome-settings-daemon. I rebooted and now when I login, gnome-settings-daemon is using > 50% of the cpu in an apparent infinite loop. Version-Release number of selected component (if applicable): gnome-settings-daemon-2.26.1-10.fc11.x86_64 How reproducible: I've only logged in once so far with the new version. I'll check again in a little while and update this bug. Steps to Reproduce: 1.yum update 2.reboot 3.login Actual results: I see the cpu usage really high, run top, and find gnome-settings-daemon is the culprit. Expected results: A lot less than 50% usage :-). Additional info: I'm not running a gnome or KDE desktop, but I am forced to start gnome-settings-daemon to get font settings to work in any gtk apps I happen to run my .xsession file gets dbus started then runs: /usr/libexec/gnome-settings-daemon & This has always worked fine in the past.
OK, I can verify that it happens every time I login, and that a new user, using a regular old gnome session also gets the same 50% cpu usage.
And if I run it from a terminal, I get this spewing out as fast as it can scroll the screen: ** (gnome-settings-daemon:29588): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:29588): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:29588): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:29588): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:29588): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:29588): WARNING **: Connection failed, reconnecting... ...
Attaching to a runaway program shows this as the only interesting thread: (gdb) bt #0 0x00007fb317d8cb0d in pthread_join (threadid=140407023286544, thread_return=0x0) at pthread_join.c:89 #1 0x00007fb313230483 in asyncns_free () from /usr/lib64/libasyncns.so.0 #2 0x00007fb313879407 in socket_client_free (c=0x20eaa20) at pulsecore/socket-client.c:328 #3 0x00007fb313879537 in pa_socket_client_unref (c=0x20eaa20) at pulsecore/socket-client.c:341 #4 0x00007fb3138784ba in do_call (c=0x20eaa20) at pulsecore/socket-client.c:176 #5 0x00007fb3138788bb in connect_io_cb (m=0x200a790, e=0x2102200, fd=26, f=12, userdata=0x20eaa20) at pulsecore/socket-client.c:199 #6 0x00007fb313ce7c86 in dispatch_func (source=0x200a730, callback=0, userdata=0x0) at pulse/glib-mainloop.c:585 #7 0x00007fb31ac8190e in g_main_dispatch (context=<value optimized out>) at gmain.c:1824 #8 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2377 #9 0x00007fb31ac850e8 in g_main_context_iterate (context=0x1fb2a40, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2455 #10 0x00007fb31ac85535 in IA__g_main_loop_run (loop=0x2041390) at gmain.c:2663 #11 0x00007fb31d2702b7 in IA__gtk_main () at gtkmain.c:1205 #12 0x0000000000404395 in main (argc=1, argv=0x7fff960429e8) at main.c:489 I subspect from the "pulse" in the names of files above that it is attempting to reconnect over and over to the pulseaudio server, which is not running (or even installed) on my system. Going into gconf-editor and disabling all plugins except the one for "fonts" which is the only thing I want the daemon to fool with seems to have tamed it. If the sound plugin is going to depend on pulse, maybe it should be separately packaged with pulse so it can be removed when a yum erase pulseaudio removes all the other bits.
I too have no pulse installed, and in gconf editor, I disabled each plugin, one at a time, in /apps/gnome_settings_daemon/plugins, and found the media-keys plugin to be the culprit, driving the cpu up. Disabling it seems to have fixed it.
Created attachment 361885 [details] Error report from gnome-settings-daemon The crash report from gnome-settings-daemon. I also have F11, and I don't use pulseaudio. Disabling media-keys plugin from gconf-editor frees the 50% CPU occupied by gnome-settings-daemon, but the daemon itself crashes. The crash report is given in this attachment. If I try to restart the daemon directly, it kills my X session.
any koji build? this bug makes my desktop unusable:-(
gnome-settings-daemon-2.26.1-11.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/gnome-settings-daemon-2.26.1-11.fc11
gnome-settings-daemon-2.26.1-11.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gnome-settings-daemon'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9904
Installing gnome-settings-daemon-2.26.1-11.fc11 does seem to have fixed the cpu usage problem when pulseaudio is not running/installed.
gnome-settings-daemon-2.26.1-11.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 527503 has been marked as a duplicate of this bug. ***
gnome-settings-daemon-2.26.1-11.fc11 fixed the problem for me.