Gnome-settings-daemon sometimes doesn't start

Hey guys. I have an occasional problem where the gnome-settings-daemon doesn't start on login. If I log out and then back in it usually starts. Or, I can run it by hand and everything works fine. It's not a big deal, but it's a little annoying. Has anybody run into this or does anybody know of a log file or something I can check to see why it doesn't come up?
Thanks
-mS
Last edited by aglarond (2009-01-25 01:01:02)

I had this problem, and I have a very fresh arch install; no old homedir, and gnome was installed at version 2.24.1 (current).
However the problem seems to have gone away once I cleared out the files in my $HOME/.config/autostart/
That directory had some .desktop files, including gnome-settings-daemon-helper.desktop (but not gnome-settings-daemon.desktop!).
Actually I find it weird that gnome-settings-daemon.desktop resides (on my system) in /etc/xdg/autostart, whereas gnome-settings-daemon-helper.desktop is in /usr/share/gnome/autostart/.
I'm not sure what the significance of any of this is, or if my entire experience (rm ~/.config/autostart/*) even makes sense. But see if it works for you
Edit: Nevermind, I still have this problem happen sporadically; the above solved nothing, it seems
Any ideas how we can debug this? How can I trace exactly what gnome-session is doing?
Last edited by infohigh (2009-01-29 05:26:16)

Similar Messages

  • GTK Theme :: X-Forwarding :: gnome-settings-daemon

    Just wondering if anyone else has come across an error like this.  Every GTK application I run using X-Forwarding looks really bad (small fonts, old boxy gnome 2.0 theme).  When I attempt to start gnome-appearance properties (also over ssh, as there is no screen connected to the server), I get the following dialog box:
    Unable to start the settings manager 'gnome-settings-daemon'.
    Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with Bonobo, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager.
    I first tried to manually start gnome-settings-daemon, which runs for about 1 second before it quits.  During that second all my windows take on the correct theme and fonts.  The debug output is confusing and looks like it's crashing right before / after it tries to load a keyboard manager.
    matt@bender ~ $ gnome-settings-daemon --no-daemon --debug
    Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
    Xlib: extension "RANDR" missing on display "localhost:10.0".
    Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
    Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
    Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
    Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
    ** (gnome-settings-daemon:14301): DEBUG: Successfully connected to D-Bus
    ** (gnome-settings-daemon:14301): DEBUG: Starting settings manager
    ** (gnome-settings-daemon:14301): DEBUG: Loading settings plugins from dir: /usr/lib/gnome-settings-daemon-2.0/
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Media keys' file='/usr/lib/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin' location='media-keys'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/media-keys for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Typing Break' file='/usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin' location='typing-break'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/typing-break for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Font' file='/usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin' location='font'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/font for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Keyboard' file='/usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin' location='keyboard'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keyboard for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Clipboard' file='/usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin' location='clipboard'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/clipboard for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/background.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Background' file='/usr/lib/gnome-settings-daemon-2.0/background.gnome-settings-plugin' location='background'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/background for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Mouse' file='/usr/lib/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin' location='mouse'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/mouse for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/housekeeping.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Housekeeping' file='/usr/lib/gnome-settings-daemon-2.0/housekeeping.gnome-settings-plugin' location='housekeeping'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/housekeeping for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/screensaver.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Screensaver' file='/usr/lib/gnome-settings-daemon-2.0/screensaver.gnome-settings-plugin' location='screensaver'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/screensaver for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='X Settings' file='/usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin' location='xsettings'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xsettings for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Accessibility Keyboard' file='/usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin' location='a11y-keyboard'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/a11y-keyboard for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Dummy' file='/usr/lib/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin' location='dummy'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/dummy for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='XRandR' file='/usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin' location='xrandr'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrandr for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/sound.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Sound' file='/usr/lib/gnome-settings-daemon-2.0/sound.gnome-settings-plugin' location='sound'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/sound for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Keybindings' file='/usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin' location='keybindings'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keybindings for changes
    ** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='X Resource Database' file='/usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin' location='xrdb'
    ** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrdb for changes
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298050 initialising
    ** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libxrandr.so
    ** (gnome-settings-daemon:14301): DEBUG: Registering GsdXrandrPlugin
    ** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdXrandrPlugin
    ** (gnome-settings-daemon:14301): DEBUG: GsdXrandrPlugin initializing
    ** (gnome-settings-daemon:14301): DEBUG: Activating xrandr plugin
    ** (gnome-settings-daemon:14301): DEBUG: Starting xrandr manager
    ** (gnome-settings-daemon:14301): WARNING **: Unable to start xrandr manager: Failed to initialize XRandR extension
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated xrandr
    ** (gnome-settings-daemon:14301): DEBUG: Plugin xrandr: active
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x82980a0 initialising
    ** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libxsettings.so
    ** (gnome-settings-daemon:14301): DEBUG: Registering GnomeXSettingsPlugin
    ** (gnome-settings-daemon:14301): DEBUG: Creating object of type GnomeXSettingsPlugin
    ** (gnome-settings-daemon:14301): DEBUG: GnomeXSettingsPlugin initializing
    ** (gnome-settings-daemon:14301): DEBUG: Activating xsettings plugin
    ** (gnome-settings-daemon:14301): DEBUG: Starting xsettings manager
    ** (gnome-settings-daemon:14301): DEBUG: Setting GTK modules 'canberra-gtk-module:gnomebreakpad'
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated xsettings
    ** (gnome-settings-daemon:14301): DEBUG: Plugin xsettings: active
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298140 initialising
    ** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libsound.so
    ** (gnome-settings-daemon:14301): DEBUG: Registering GsdSoundPlugin
    ** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdSoundPlugin
    ** (gnome-settings-daemon:14301): DEBUG: GsdSoundPlugin initializing
    ** (gnome-settings-daemon:14301): DEBUG: Activating sound plugin
    ** (gnome-settings-daemon:14301): DEBUG: Starting sound manager
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated sound
    ** (gnome-settings-daemon:14301): DEBUG: Plugin sound: active
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298190 initialising
    ** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libfont.so
    ** (gnome-settings-daemon:14301): DEBUG: Registering GsdFontPlugin
    ** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdFontPlugin
    ** (gnome-settings-daemon:14301): DEBUG: GsdFontPlugin initializing
    ** (gnome-settings-daemon:14301): DEBUG: Activating font plugin
    ** (gnome-settings-daemon:14301): DEBUG: Starting font manager
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated font
    ** (gnome-settings-daemon:14301): DEBUG: Plugin font: active
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298200 initialising
    ** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libbackground.so
    ** (gnome-settings-daemon:14301): DEBUG: Registering GsdBackgroundPlugin
    ** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdBackgroundPlugin
    ** (gnome-settings-daemon:14301): DEBUG: GsdBackgroundPlugin initializing
    ** (gnome-settings-daemon:14301): DEBUG: Activating background plugin
    ** (gnome-settings-daemon:14301): DEBUG: Starting background manager
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated background
    ** (gnome-settings-daemon:14301): DEBUG: Plugin background: active
    ** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298250 initialising
    ** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libkeyboard.so
    ** (gnome-settings-daemon:14301): DEBUG: Registering GsdKeyboardPlugin
    ** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdKeyboardPlugin
    ** (gnome-settings-daemon:14301): DEBUG: GsdKeyboardPlugin initializing
    ** (gnome-settings-daemon:14301): DEBUG: Activating keyboard plugin
    ** (gnome-settings-daemon:14301): DEBUG: Starting keyboard manager
    The program 'gnome-settings-daemon' received an X Window System error.
    This probably reflects a bug in the program.
    The error was 'BadClass, invalid event class'.
    (Details: serial 145 error_code 137 request_code 134 minor_code 6)
    (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() function.)
    [1238394881,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
    Sorry for the long output, I wasn't sure if some small bit of information in there could be relevant.  I'm just kinda hoping that someone else has had this problem and came up with an easy fix.
    -Matt

    Hi!
    You might be interested in the workaround found here:
    https://bugs.launchpad.net/ubuntu/+sour … bug/199245
    It seems the gnome-settings-daemon crashes while trying to load the keyboard plugin, you might have more luck getting it to work if you deactivate the plugin. It worked here at least.
    For this, I have put this line in my session starting script.
    gconftool-2 -t bool --set /apps/gnome_settings_daemon/plugins/keyboard/active false
    I am using NX, but your problem is almost exactly like mine and NX is basically X session forwarding on steroids.
    I still don't know what this plugin affects on a gdm session, so I have this untested bit in my .gnomerc file.
    gconftool-2 -t bool --set /apps/gnome_settings_daemon/plugins/keyboard/active true
    (the plugin is reactivated)
    I am not sure that the .gnomerc file is executed when gdm starts a session, so it's a guess for now (I will try to edit later with my results).
    [EDIT]
    The command in the .gnomerc file didn't work.
    This plugin, as I thought, sets the keyboard settings, it is quite useful to have it activated.
    The only workaround I found (for now) is to test if this is an NX session and if not, activate it. (I don't know if it is doable to check if it is an X11-Forwarding session.)
    [/EDIT]
    [EDIT2]
    Oh wow, old post! In this date of February 19th 2010, I cam across this post.
    I had a similar problem and had it resolved with my old self's help today. (I had a hard time searching and found this post... I feel dumb).
    Always within an NX session, I had a similar problem. The gnome-settings-daemon still wouldn't start, but with the updates in GNOME, the message changed. Here is the new message:
    Unable to start the settings manager 'gnome-settings-daemon'.
    Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with DBus, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager.
    This is the other key you want to deactivate with NX.
    /apps/gnome_settings_daemon/plugins/xrandr/active
    The keyboard key still needs to be deactivated.
    Cheers for any internet dweller who finds this!
    [/EDIT2]
    These two modifications will work in any session scripts, but you have to disable the plugin before the gnome-settings-daemon runs, but I think activating it after is not a problem (try activating it when gnome-settings-daemon is running, it will crash under NX).
    Anyway, it could be interesting to link to that wiki page you will write here!
    Good luck!
    Oh, I'm putting some keywords here for search engines to pick this up as the problem seems to be common accross many remote protocols like: VNC gnome-settings-daemon, X11 over SSH gnome-settings-daemon and X over SSH gnome-settings-daemon. xrandr gnome-settings-daemon crash.
    Last edited by samueldr (2010-02-19 05:22:04)

  • Error starting the GNOME Settings Daemon

    After a full system upgrade of about 500mb, I now get this error when Gnome is started. Also, im kinda new to this...
    "There was an error starting the GNOME Settings Daemon.
    Some things, such as themes, sounds, or background settings may not work correctly.
    The last error message was:
    The name org.gnome.SettingsDaemon was not provided by any .service files
    GNOME will still try to restart the Settings Daemon next time you log in."
    The things is, my background and other desktop stuff is still in their place. But my keyboard has gone back to its default setting and the drivers for my wireless isnt getting loaded. I also have problems playing music with Amarok.
    After the full upgrade of my system I installed compiz-fusion and AWM, but they arent started when i boot. Could they be a problem?
    I looked at some issues with similar error messages, where they downgraded the gnome-settings-tools, how do I do that?

    Hi there!
    I copied the from where pacman generates the fallback version before starting to upgrade.
    [2008-05-30 18:44] :: Begin build
    [2008-05-30 18:44] :: Parsing hook [base]
    [2008-05-30 18:44] :: Parsing hook [udev]
    [2008-05-30 18:44] :: Parsing hook [autodetect]
    [2008-05-30 18:44] :: Parsing hook [pata]
    [2008-05-30 18:44] :: Parsing hook [scsi]
    [2008-05-30 18:44] :: Parsing hook [sata]
    [2008-05-30 18:44] :: Parsing hook [usbinput]
    [2008-05-30 18:44] :: Parsing hook [keymap]
    [2008-05-30 18:44] :: Parsing hook [filesystems]
    [2008-05-30 18:44] :: Generating module dependencies
    [2008-05-30 18:44] :: Generating image '/boot/kernel26.img'...SUCCESS
    [2008-05-30 18:44] ==> SUCCESS
    [2008-05-30 18:44] ==> Building image "fallback"
    [2008-05-30 18:44] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
    [2008-05-30 18:44] :: Begin build
    [2008-05-30 18:44] :: Parsing hook [base]
    [2008-05-30 18:44] :: Parsing hook [udev]
    [2008-05-30 18:44] :: Parsing hook [pata]
    [2008-05-30 18:44] :: Parsing hook [scsi]
    [2008-05-30 18:44] :: Parsing hook [sata]
    [2008-05-30 18:44] :: Parsing hook [usbinput]
    [2008-05-30 18:44] :: Parsing hook [keymap]
    [2008-05-30 18:44] :: Parsing hook [filesystems]
    [2008-05-30 18:44] :: Generating module dependencies
    [2008-05-30 18:44] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
    [2008-05-30 18:44] ==> SUCCESS
    [2008-05-30 18:44] upgraded kernel26 (2.6.24.1-2 -> 2.6.25.4-1)
    [2008-05-30 18:44] upgraded ipw3945 (1.2.2-7 -> 1.2.2-10)
    [2008-05-30 18:44] upgraded libdvdnav (0.1.10-2 -> 0.1.10-3)
    [2008-05-30 18:44] upgraded libebml (0.7.7-1 -> 0.7.8-1)
    [2008-05-30 18:44] upgraded libgail-gnome (1.20.0-1 -> 1.20.0-2)
    [2008-05-30 18:44] upgraded libnetworkmanager (0.6.5-1 -> 0.6.6-1)
    [2008-05-30 18:44] upgraded libnl (1.0pre6-1 -> 1.1-1)
    [2008-05-30 18:44] upgraded libsamplerate (0.1.2-4 -> 0.1.3-1)
    [2008-05-30 18:44] upgraded licenses (2.3-1 -> 2.4-1)
    [2008-05-30 18:44] upgraded lvm2 (2.02.33-1 -> 2.02.36-1)
    [2008-05-30 18:44] upgraded man-pages (2.77-1 -> 2.79-1)
    [2008-05-30 18:45] Updating font cache... done.
    [2008-05-30 18:45] upgraded ttf-dejavu (2.23-1 -> 2.25-1)
    [2008-05-30 18:45] upgraded mplayer (1.0rc2-2.1 -> 1.0rc2-3)
    [2008-05-30 18:45] upgraded nautilus-cd-burner (2.20.0-1 -> 2.22.1-1)
    [2008-05-30 18:45] upgraded networkmanager (0.6.5-3 -> 0.6.6-1)
    [2008-05-30 18:45] In order to use the new nvidia module, exit Xserver and unload it manually.
    [2008-05-30 18:45] upgraded nvidia (169.09-2 -> 169.12-4)
    [2008-05-30 18:45] upgraded opera (9.25-2 -> 9.27-1)
    [2008-05-30 18:45] upgraded orca (2.20.3-1 -> 2.22.0-1)
    [2008-05-30 18:45] upgraded pcmciautils (014-3 -> 014-4)
    [2008-05-30 18:45] upgraded perlxml (2.34-4 -> 2.36-1)
    [2008-05-30 18:45] upgraded perl-xml-simple (2.18-1 -> 2.18-2)
    [2008-05-30 18:45] upgraded printproto (1.0.3-1 -> 1.0.4-1)
    [2008-05-30 18:45] upgraded pycairo (1.4.0-3 -> 1.4.12-1)
    [2008-05-30 18:45] upgraded qt (4.3.3-4 -> 4.3.4-1)
    [2008-05-30 18:46] upgraded seahorse (2.20.3-1 -> 2.22.1-1)
    [2008-05-30 18:46] upgraded sound-juicer (2.20.1-1 -> 2.22.0-1)
    [2008-05-30 18:46] upgraded tar (1.19-2 -> 1.20-2)
    [2008-05-30 18:46] installed ndesk-dbus (0.6.0-1)
    [2008-05-30 18:46] installed ndesk-dbus-glib (0.4.1-1)
    [2008-05-30 18:46] installed mono-addins (0.3.1-2)
    [2008-05-30 18:46] upgraded tomboy (0.8.1-1 -> 0.10.1-1)
    [2008-05-30 18:46] upgraded totem-plparser (2.21.91-1 -> 2.22.2-1)
    [2008-05-30 18:46] installed libepc (0.3.5-1)
    [2008-05-30 18:46] installed python-elementtree (1.2.6-2)
    [2008-05-30 18:46] installed python-gdata (1.0.11.1-1)
    [2008-05-30 18:46]
    [2008-05-30 18:46] ==> Totem has been built with GStreamer. By default, only plugins from
    [2008-05-30 18:46] ==> gst-plugins-good and gst-plugins-base are installed.
    [2008-05-30 18:46] ==>
    [2008-05-30 18:46] ==> To play additional media formats, more plugins are available from
    [2008-05-30 18:46] ==> gstreamer0.10-ugly-plugins, gstreamer0.10-bad-plugins
    [2008-05-30 18:46] ==> and gstreamer0.10-ffmpeg packages.
    [2008-05-30 18:46] ==>
    [2008-05-30 18:46] ==> There's also a xine build of Totem available, install totem-xine instead
    [2008-05-30 18:46] ==> of this package if you want xine to play your media files.
    [2008-05-30 18:46]
    [2008-05-30 18:46] upgraded totem (2.20.1-3 -> 2.22.2-1)
    [2008-05-30 18:46] upgraded totem-plugin (2.20.1-3 -> 2.22.0-1)
    [2008-05-30 18:46] Remove vi related symlinks ...
    [2008-05-30 18:46] Create vi related symlinks...
    [2008-05-30 18:46] Updating vi help tags...done.
    [2008-05-30 18:46] upgraded vi (7.1.228-1 -> 7.1.267-1)
    [2008-05-30 18:46] upgraded vino (2.20.1-1 -> 2.22.1-1)
    [2008-05-30 18:46] upgraded vlc (0.8.6d-2 -> 0.8.6f-3)
    [2008-05-30 18:46] upgraded wget (1.11-1 -> 1.11.2-1)
    [2008-05-30 18:47] upgraded xfsprogs (2.9.4-2 -> 2.9.7-1)
    [2008-05-30 18:47] upgraded xorg-apps (1.0.3-2 -> 1.0.3-3)
    [2008-05-30 18:47] upgraded xproto (7.0.11-1 -> 7.0.12-1)
    [2008-05-30 18:47] upgraded xtrans (1.0.4-1 -> 1.2-1)
    [2008-05-30 18:47] upgraded zenity (2.20.1-1 -> 2.22.1-1)
    Last edited by derelic (2008-05-31 16:17:58)

  • Run gnome-settings-deaemon on KDE 4 start

    Although I run KDE 4 I also use some GNOME applications because they are better. Most of them require gnome-settings-daemon to access configuration data.  It is bothersome to run gnome-settings-daemon manually from console.Do you know a simple way to do it automatically on KDE start up? I am using GDM to start KDE.

    kde4 runs programs in ~/.kde4/Autostart automatically on start. So just link gnome-settings-daemon there:
    ln -s /usr/bin/gnome-settings-daemon ~/.kde4/Autostart

  • Random freezes due to gnome-settings-daemon

    Hello,
      I've been experiencing frequent and random crashes during which the entire system freezes over a several-second period due to gnome-settings-daemon quickly consuming all available ram.  During the crashes the mouse, keyboard, sound, and screen all become frozen, and I cannot trigger suspend, hibernate, shutdown, or switch virtual terminals.  gnome-settings-daemon memory usage rises to 1.2GB.  Nothing stands out in journalctl except for the usual general abundance of seemingly unrelated error messages, and I can't link the crash to any obvious trigger.  The only way out is cutting the power.  I've tried limiting /tmp size, killing the daemon, and closing applications in the brief time before total unusability, and none of these things has had any effect... According to a Google search, this was a problem with a recent version of the daemon, but it was apparently fixed.  Has anybody else experienced this?  Thanks.
    Update:  It's happening about once or twice an hour.  I'll just go to move the mouse and it won't.  Sound sometimes keeps functioning choppily for up to ~30 seconds.
    Last edited by Aestus (2013-12-19 15:22:40)

    Use lxappearance to set your gtk settings.  There are some other ones too, like gtk-chtheme, gtk-theme-switch2, and gtk2_prefs.  I like lxappearance, personally.
    https://wiki.archlinux.org/index.php/GTK+

  • [SOLVED] gnome-settings-daemon problem after pacman -Syu

    Today after updating my hp laptop with pacman -Syu, I noticed that I lost a few of my multimedia key shortcuts. When I tried to fix this with System->Preferences->Keyboard Shortcuts, I get this error:
    Unable to start the settings manager 'gnome-settings-daemon'.
    Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with Bonobo, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager.
    The keyboard shortcut menu comes up as normal, and seems to work like it should for everything but the multimedia keys. I get the same error when clicking on the Appearance & Keyboard menus.
    I remember pacman asking me if I wanted to replace gail with gtk2. Could that have anything to do with it?
    Any ideas?
    Thanks!!!!
    Last edited by bebeababa (2008-10-23 17:08:13)

    JGC wrote:Log out from gnome and login again, this should fix your issues.
    Tried it, no change.
    I forgot to mention that running "gnome-settings-daemon" in a termal produces:
    ** ERROR **: You can only run one xsettings manager at a time; exiting
    aborting...
    Aborted
    ... and that the pstree shows a "gnome-settings-" entry.
    Any other ideas?

  • Gnome-settings-daemon: Fatal IO error 11

    When I logout the gnome, there will be always a warning.
    Why I call it warning is that this issue only occurs when I shutdown the X.
    What is the solution?
    CODE:
    waiting for X server to shut down gnome-settings-daemon: Fatal IO error 11 (Resource temporarity unavailable) on X server :0.0.
    gnome-screensaver: Fatal IO erro 11 (Resource temporarily unavailabe) on X server :0.0.
    gtk-window-decorator: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
    Screenshot:
    Last edited by aeonlove (2010-11-01 22:16:52)

    zozi56 wrote:Can you reproduce the problem without Skype, Bastian?
    From what I remember I have also had this issue when Skype wasn't open.
    Yesterday my computer started up beeping - I took the harddisk out and it started normally (initramfs tho). Then I put it back in and the laptop have been running fine so far. I suspect it might just have been a bad connection, but I am giving it time..
    EDIT: Still experiencing the issue..
    Last edited by Bastian (2014-01-19 18:09:08)

  • 'gnome-settings-daemon.desktop' killed by signal 11

    I feel like a total n00b (so I probably am) but this is bothering me for quite some time now.
    Whenever I start gnome (3.16.2) I get the stupid "Oh no!" window, saying something is wrong. It is still possible to start applications but one screen (of the two) is covered by the annoying message.
    This happens on a completely fresh installed machine. LXDE runs fine, gnome (on wayland, on X) seems to run fine, except for that message. On another machine (Dell XPS13) this issue is not present.
    journalctl /usr/bin/gnome-session
    Jun 06 14:03:12 kastje gnome-session[10740]: (gnome-settings-daemon:10975): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed
    Jun 06 14:03:12 kastje gnome-session[10740]: (gnome-settings-daemon:10975): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value != NULL' failed
    Jun 06 14:03:12 kastje gnome-session[10740]: gnome-session[10740]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly
    Jun 06 14:03:12 kastje gnome-session[10740]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly
    Jun 06 14:03:12 kastje gnome-session[10740]: Unrecoverable failure in required component gnome-settings-daemon.desktop
    Jun 06 14:03:12 kastje gnome-session[10740]: gnome-session[10740]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 11
    Anyone out there able to point out the dumb mistake I am making?
    Last edited by davidsmit (2015-06-06 12:40:06)

    Another test conducted:
    Reinstall completely, create new user (with empty home). Same result.
    Also, after install of gnome-initial-setup, that still runs, on top of the error message! Baffles me. Screenshot.

  • Gnome-settings-daemon + gnome 3.2 + openbox

    After gnome 3.2 upgrade, I can't run gnome-settings-daemon by itself anymore.
    I used to use it with openbox, mainly for getting themes loaded (which I am achieving with
    settings.ini now), but more important, to get my fn shortcuts working in my laptop.
    Any ideas are welcome.

    Mad Fish wrote:
    Seems to work for me (I'm using Openbox standalone). Started with:
    /usr/lib/gnome-settings-daemon/gnome-settings-daemon
    I was trying just:
    /usr/lib/gnome-settings/daemon
    Works now.
    Mad Fish wrote:Also, you can live without it. You can use xsettingsd for themes/icons/fonts configuration, feh for desktop background, and assign hotkeys in obconf for media keys. That's what works for me.
    I already used feh. It does the job just fine.
    I found xsettingsd in AUR. I'm going to give it a try.
    About hotkeys in obconf, I didn't find such option.
    Thanks.
    Last edited by FernandoBasso (2011-10-02 15:42:21)

  • NX and gnome-settings-daemon

    Hi all,
    I'm new here and I'm using Arch for a few months now. I came (in fact I never left it) from Gentoo, so I found the Arch procedures somewhat familiar. I'm using the x86_x64 flavor as my desktop box, which is an Athlon 64 3200+.
    I recently noticed while accessing my box through NX that suddenly had broken the gnome themes and stuff like that. Just by running from a shell "gnome-settings-daemon" I saw the following error:
    The error was 'XI_BadClass (invalid Class parameter)'.
    (Details: serial 158 error_code 133 request_code 131 minor_code 6)
    (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() function.)
    So I ran gnome-settings-daemon with the --sync parameter:
    ** (gnome-settings-daemon:9066): WARNING **: Unable to start xrandr manager: unhandled X error while getting the range of screen sizes
    [pega@rei ~]$ The program 'gnome-settings-daemon' received an X Window System error.
    This probably reflects a bug in the program.
    The error was 'XI_BadClass (invalid Class parameter)'.
    (Details: serial 221 error_code 133 request_code 131 minor_code 6)
    (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() function.)
    A quick googling about XI_BadClass led me to https://bugs.launchpad.net/ubuntu/jaunt … bug/409621. Browsing a bit I found this: http://www.rpmfind.net/linux/RPM/opensu … 86_64.html.
    The point is that I just want to try the latest version (or at least that version) of libxklavier. The problem is that i don't want to go the ./configure && make && make install way, for my system's cleanliness sake. I looked for libxklavier in ABS but i found the 3.9 version.
    Can you give me a hint?
    Thanks in advance,
    Paul.

    Thanks AndyRTR, I managed to install the 4.0 version modifying the PKGBUILD from ABS. After a reboot (I'd got to be sure) I accessed again my box from NX and gnome-settings-daemon seemed to work fine at least in aspect (it loaded the gnome themes) but it spitted out this:
    ** (gnome-settings-daemon:5100): WARNING **: Unable to start xrandr manager: unhandled X error while getting the range of screen sizes
    ** (gnome-settings-daemon:5100): WARNING **: libxklavier.so.12: cannot open shared object file: No such file or directory
    ** (gnome-settings-daemon:5100): WARNING **: Cannot load plugin 'Keyboard' since file '/usr/lib/gnome-settings-daemon-2.0/libkeyboard.so' cannot be read.
    ** (gnome-settings-daemon:5100): WARNING **: Error activating plugin 'Keyboard'
    So I just wanted to be sure that my layout were working (I'm using OpenBox without the startup script):
    [pega@rei ~]$ setxkbmap us intl
    [pega@rei ~]$ á
    As you can see the layout is working fine. So, what's happening here?
    Thanks!
    Update:
    I thought I could sing victory but I left my box alone a bit and when gnome-screensaver activated itself, just went crazy. At any mouse movement or typing any single key, the screen blinked alternating black with the default (green) gnome wallpaper. To recover my computer's control I had to kill gnome-screensaver from a tty; also, I noticed that the layout was broken too (it was reset to default 'us').
    So I'm rollbacking right now until knowing more about how to workaround this.
    Last edited by PeGa! (2009-10-08 21:06:35)

  • [WORKAROUND] After update: gnome-settings-daemon can't find dbus?

    Hey all,
    first of all, the problem started after the update yesterday. At the moment, my system is up-to-date without any testing packages. My dbus is started in /etc/rc.conf by the entry of hal. It certainly runs according to `ps ax`. But now after login to gnome it takes some minutes (which is longer than usual) and then the following message shows up:
    There was an error starting the GNOME Settings Daemon.
    Some things, such as themes, sounds, or background settings may not work correctly.
    The last error message was:
    Failed to connect to socket /tmp/dbus-sxaWRBhjCI: Connection refused
    GNOME will still try to restart the Settings Daemon next time you log in.
    The funny thing is, that /tmp/dbus-sxaWRBhjCI does not exist in /tmp, see here:
    andi@hbar> ll /tmp
    total 240K
    drwxrwxrwt 10 root root 196K 2008-10-20 13:57 ./
    drwxr-xr-x 19 root root 4.0K 2008-10-02 17:37 ../
    drwxr-xr-x 2 root root 4.0K 2008-10-20 13:49 hsperfdata_root/
    drwxrwxrwt 2 root root 4.0K 2008-10-20 13:50 .ICE-unix/
    drwx------ 2 andi users 4.0K 2008-10-20 13:50 keyring-LKXmSd/
    drwx------ 2 andi users 4.0K 2008-10-20 13:52 orbit-andi/
    drwx------ 2 nobody gdm 4.0K 1970-01-01 01:00 orbit-nobody/
    drwx------ 2 andi users 4.0K 2008-10-20 13:49 ssh-ZYPRoS6800/
    drwx------ 2 andi users 4.0K 2008-10-20 13:50 virtual-andi.agPvKH/
    -r--r--r-- 1 root root 11 2008-10-20 13:49 .X0-lock
    drwxrwxrwt 2 root root 4.0K 2008-10-20 13:49 .X11-unix/
    My gnome session starts anyway but e.g. the panel looks in default style. The funniest thing is in the end, that I can start gnome-settings-daemon in terminal (after gnome started) and everything starts looking as it was. See here:
    andi@hbar> gnome-settings-daemon ~
    ** (gnome-settings-daemon:7538): WARNING **: libgnomekbd.so.2: cannot open shared object file: No such file or directory
    ** (gnome-settings-daemon:7538): WARNING **: Cannot load plugin 'Keyboard' since file '/usr/lib/gnome-settings-daemon-2.0/libkeyboard.so' cannot be read.
    ** (gnome-settings-daemon:7538): WARNING **: Error activating plugin 'Keyboard'
    xrdb: "*Label.background" on line 220 overrides entry on line 150
    xrdb: "*Text.background" on line 226 overrides entry on line 191
    xrdb: "*Label.foreground" on line 232 overrides entry on line 151
    xrdb: "*Text.foreground" on line 238 overrides entry on line 192
    Can anyone help me in fixing this? Or does anyone experiencing the same problem? Thanks in advance.
    Edit: I tried the gnome-session-daemon from testing (and its dependencies), but this caused that gnome did not start at all!
    Last edited by aneiser (2008-10-20 16:58:37)

    same problem...
    Der Konfigurationsserver konnte nicht kontaktiert werden; mögliche Fehlerquellen sind, dass TCP/IP für ORBit nicht aktiviert ist oder auf Grund eines Systemabsturzes alte NFS-Sperren gesetzt sind. Unter http://www.gnome.org/projects/gconf/ erhalten Sie weitere Informationen (Details -  1: Verbindung zur Sitzung konnte nicht abgerufen werden: Failed to connect to socket /tmp/dbus-GQ8eIpBcxB: Verbindungsaufbau abgelehnt)
    Beim Starten des GNOME-Einstellungsdämons ist ein Fehler aufgetreten.
    Möglicherweise funktionieren einige Dinge, wie z.B. Themen, Klänge oder Hintergrundeinstellungen nicht korrekt.
    Die letzte Fehlermeldung war:
    Failed to connect to socket /tmp/dbus-KmOC2nTOQD: Verbindungsaufbau abgelehnt
    Beim nächsten Anmelden wird GNOME weiterhin versuchen, den Einstellungsdämon neu zu starten
    Last edited by msart2k (2008-10-20 15:38:42)

  • Gnome-settings-daemon and freeNX problem

    Gnome-settings-daemon refuses to start in remote NX session. When I login locally everything is ok.
    Experimentally I've found that if keyboard plugin of gnome-settings-daemon is deactivated through gconf everything works fine. Except keyboard of course (: (all keyboard settings are lost ): ).
    The problem appeared after the reboot of the computer, which runs x86_64 Arch, with uptime about a month. Can't figure it myself, please help!
    Last edited by angrycore (2009-04-24 17:31:44)

    I've just disabled keyboard plugin and added simple script to autostart which configures keyboard using setxkbmap. Not that beautiful solution, but works.

  • Gnome-settings-daemon no where to be found

    Hello again .. Ive read about this posted earlier but I cant find a solution to that problem anywhere..
    Ok so Ive been using linux for a few months now, and only through KDE. Ive tried several other WM .. actually probably every one of them at least once, all but gnome.
    Now I do not have an internet connection, so just installing gnome through scripts or whatever wasnt an option. SO I have downloaded all packages and dependencies (yes, its got to be something like 60 files) manually and and installed them all.. libgnome gnome-desktop libbonoboui bla blah etc etc etc ..
    Now, when i run gnome-session I get an error about loading gnome-settings-daemon.. I dont have that program anywhere on my computer. It doesnt seem to be in any of the gnome-* packages ive downloaded either ..
    And when i try to installed metacity I get an error about unable to load a certain file .. IO error or something .. like the package is corrupt or whatever ..
    Anyway, im asking just out of curiousity as I have given up on gnome .. i was just intrigued but Ill stick to kdemod for the time being. When I get my new laptop, kde4 will be out my then and Ill probably go with that.
    Thanks

    Hi pedepy,
    gnome-settings-daemon is owned by control-center package

  • [SOLVED]Failed to build gnome-settings-daemon-nopulse

    Hello,
    i hope its the right place and somebody can help me.
    I tried to install "gnome-settings-daemon-nopulse" from the aur and shortly after the build begins it stopped with a build failure.
    The Full log is:
    patching file plugins/common/Makefile.am
    patching file plugins/common/gsd-power-helper.c
    patching file plugins/common/gsd-power-helper.h
    patching file plugins/media-keys/gsd-media-keys-manager.c
    patching file plugins/power/gsd-power-manager.c
    Hunk #14 succeeded at 3444 (offset 2 lines).
    Hunk #15 succeeded at 3685 (offset 2 lines).
    Hunk #16 succeeded at 3975 (offset 2 lines).
    Hunk #17 succeeded at 4008 (offset 2 lines).
    Hunk #18 succeeded at 4121 (offset 2 lines).
    Hunk #19 succeeded at 4155 (offset 1 line).
    Hunk #20 succeeded at 4171 (offset 1 line).
    Hunk #21 succeeded at 4178 (offset 1 line).
    Hunk #22 succeeded at 4224 (offset 1 line).
    gnome-settings-daemon/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
    parallel-tests: error: required file './test-driver' not found
    parallel-tests: 'automake --add-missing' can install 'test-driver'
    plugins/media-keys/cut-n-paste/Makefile.am:5: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
    Has someone an idea how to fix it?
    greets
    odin89
    Last edited by odin89 (2013-01-30 14:41:41)

    One way is to add the "--add-missing" flag the automake line in the PKGBUILD.
    But as far as why it happens, maybe someone else can chime in. When I try it in a clean chroot, the PKGBUILD "just works" as is. On my live systems, I get the same error unless I add "--add-missing."
    Last edited by tdy (2013-01-30 13:36:18)

  • Gnome settings daemon and .Xdefaults?!

    Hey,
    So, apparently, if you are using gnome-settings-daemon, it overrides your .Xdefaults file.
    Is there some way to either set the same things when using gnome-settings-daemon (ie xterm fonts and looks etc)
    or is there some way to override the overriding of .Xdefaults?
    /smurfd

    .Xresources, instead of .Xdefaults?
    I know that on Debian, when I switched back to GNOME (from Openbox), my settings for urxvt were preserved and utilized.  I had them in ~/.Xresources rather than ~/.Xdefaults.  I haven't tried this on Arch yet, so I can't say for sure it works.
    It's all terribly confusing, the way xorg interacts with some DE's -- trying to find the magic combination of instructions you have to put together to get things setup the way you want without this or that overriding that or this.

Maybe you are looking for

  • At Sales order

    Hai all , Good eve, i have scenario like this Sales order is created 1st November for 200 toothpastes 100 brushes free of goods (2+1 free goods). At the time of delivery on 15th August you have shortage of brushes by 40. Offer closed on 15th August.

  • 4th gen iPod touch won't connect to computer

    I have tried it in all of my USB ports, but it will not connect at all. It's not even that It's not showing up in iTunes, It's also not charging or showing on my computer. I've only had it since December '10, please help!

  • Burning DVD files....

    Can someone please answer this question..... Which Roxio Toast app is compatible with my Macbook? I need to be able to burn .dvd/.avi files For Later Viewing, Not For Re-Sale... Macbook OSX 10.4.11 2GHz Intel 2 Duo

  • Hyperion FDM and ERPi 11.1.2.2: ORA-12504 on Import with ERPI-FIN-E

    Hi everyone, We are implementing Hyperion 11.1.2.2 FDM with HFM (Target Adapter = FM11X-G6-A) and ERPi (Source Adapter = ERPI-FIN-E) running on ODI 11.1.1.6. Backend databases are all Oracle DBs. We have been able to successfully configure ERPi and O

  • Attachments with SMTP

    Hi, I am writing an email client, and I was wondering how I might be able to send attachments using the SMTP protocol. Thanks.