Dbus/gnome-settings-manager error

This has been popping up for me on the past couple of weeks when I launch Firefox or Abiword (there's probably more). I do not use GNOME on a daily basis (I use kdemod3) so this is just annoying.
I've already reinstalled gnome-settings-daemon, dbus, dbus-core, and policykit. Any other ideas?
dbus is in DAEMONS and the system bus was running at the time these errors occur.
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-M0bpNe7zMX: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-rCx5JaJxPf: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-3PKcZlCdCx: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-0XlJdRsSfx: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-MdMHHsmZLV: Connection refused)

You will need a dbus session bus, without this, 95% of modern applications, including GNOME, won't work. KDE3 does not autostart such a thing.

Similar Messages

Gnome settings do not take, and gnome-settings-manager breaks things.

I just updated my Arch install. I hadn't done a full system upgrade since December (I think). The install went fine as far as I can tell. It broke my xorg.conf again, but it always does that, no biggie.
My biggest fight seems to be with the gnome-settings-manager. I am now getting no icons in the menus, the mouse runs extremely slow and the only way to get it to run at a normal tracking speed is to use the KDE 'systemsettings' to change it (bizarre). Also, any desktop background that I assign is essentially covered over on startup with a background color and I cannot (using any settings program in the menus) actually put something there. I'm sure there's just some confusion over what is in control of the desktop and which config file is being used, but I cannot find any other mention of this issue in the forums, and forcefully re-installing gnome has yielded no help. I also moved all my '.gnome' dirs under home to some other location, and this made no difference.
Some info:
# pacman -Q gnome-applets gnome-desktop gnome-settings-daemon gnome-session
gnome-applets 2.24.3.1-1
gnome-desktop 2.24.3-1
gnome-settings-daemon 2.24.1-1
gnome-session 2.24.3-1
When I run gnome-mouse-properties from a command line, I see this:
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Then, when I try to change the mouse acceleration:
(gnome-mouse-properties:7165): capplet-common-WARNING **: Unable to find a default value for key for /desktop/gnome/peripherals/mouse/motion_acceleration.
I'll assume it is an integer, but that may break things.
Please be sure that the associated schema is installed
(gnome-mouse-properties:7165): GConf-CRITICAL **: gconf_value_get_float: assertion `value->type == GCONF_VALUE_FLOAT' failed
(gnome-mouse-properties:7165): GConf-CRITICAL **: gconf_value_get_float: assertion `value->type == GCONF_VALUE_FLOAT' failed
Any ideas?

Just to reinforce what byte said: I had similar problems and moving .gconf worked. If it doesn't, you can also try moving .gnome2. And then if you are versed in the edition of gnome settings files, you can search and repair the faulty ones. If not (like me)... start from scratch, delete the moved dir.
It would be great if the gnome devs simplified the format of settings files (make it more like rc.conf!) and made it so they don't break so often. Maybe a system a la windows where previous versions of the registry get saved. Then upon breakage one could just bring up the last working version. Of course the best thing would be for the settings to not get corrupted in the first place.

Gnome-cups-manager error

I installed gnome-cups-manager from TUR: [staging]
The install went fine. I can't find the cups-manager anywhere in
the menus. I then tried as su
# /opt/gnome/bin/gnome-cups-manager
/opt/gnome/bin/gnome-cups-manager: error while loading shared libraries: liblinc.so.1: cannot open shared object file: No such file or directory
iI don't know how to fix this
Thanks
dk

Kind of bad news now, from the looks of it, it won't work with the new gtk or the new gnome or something else that is new on my system, as it won't compile. I will look around for patches and if anyone else can figure out how to get it to work, it would be helpful.
Kritoke

Hal/Dbus/gnome-volume-manager mount permission problem

Hello,
I have hal/dbus/gnome-volume-manager installed (of course I use gnome as DE).
I need help in configuring the permissions for automatically mounted disk/partitions.
When I connect an external USB HDD having 1 NTFS and 1 partition, these partitions are auto-mounted and the desktop icons appear for the both.
As a normal user I am able to read/write FAT partition (I think, not because I have configured anything properly, but because FAT does not support permissions on filesystem), but I am not even able to read (browse) NTFS filesystem (ERORR: You do not have permission...).
Yes, I have NTFS filesystm support enabled, because I am able to access that same NTFS partition as root.

Well, Thanks for the reply but I had not put any static entry in fstab for this external USB HDD.
Anyway, I figured out something (havn't tested it yet)
When an external USB HDD is attached ... depending storage.policy and volume.policy rules in /usr/share/hal .. the hal daemon (hald) calls fstab-sync with appropriate parameters.
fstab-sync, then, generates /etc/fstab enteries automatically (with comment=managed keyword).
I have added a user policy so that umask and gid value is set correctly. I'll test is as soon as I'll get time.
In the meanwhile if anybody have any other suggestions, please post it here.

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)

[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?

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)

Dbus/hal/gnome-volume-manager problem

I've got hal and dbus running but it doesnt even seem that gnome-volume-manager is started. I added it to my gnome session but that didnt seem to do the trick. I'm trying to be able to just plug in my usb key and ipod and have them automount. It works if I restart hal or run gnome-volume-manager from the command line but then work work again unless I restart that stuff again. Here is a cut from my fstab:
/dev/sda1 /mnt/usb auto user,noauto 0 0
/dev/sda2 /mnt/ipod auto user,noauto 0 0

Hi lhoerste,
I had this problem with automount as well. The way I fixed it was adding
dbus hal to daemons line in /etc/rc.conf. You probably did this already.
Next, when you are in the gnome desktop, stick in a cd. Nothing happens right?
Now go to preferences=>removable drives and media (I think this is what it is called. I'm not sitting infront of my computer at the moment). Then make sure that the checkboxes pertaining to "mount automatically" are checked.
Close window.
Now your cd should automount and appear on the desktop. Eject the cd by right clicking on the icon and choosing eject.
Now, restart and ***make sure you save settings*** before leaving.
Get back into the gnome desktop and plug your cd back in. It should automount now.
This is how I got automount to work for me.

Gnome power manager upgrade - nvidia sedmentation error

I am trying to use the rolling update model properly and check the web page for issues before doing my pacman Syu.
I updated gnome-power-manager (along with the other available updates) today amd immediately noticed different behaviour.
The laptop (Dell Inspiron 1720) no longer suspended when I shut the lid. I still had the shutdown menu option but... when I used it it intermittently caused segmentation fault errors in nvidia settings and stuff like Google Earth no longer worked. My graphics card is geForce 8600M GT.
Downgrading the gnome-power-manager package restored everything to working order.
Maybe I did something daft, but I'd like to know if there is something else I should have checked or if there is a problem with this package. In the meantime I've added it to IgnorePkg

i just pointing out that you can try to fix it yourself(until is fixed in our repo) by compiling gnome-power-manager using abs and add that option to the ./configure within PKGBUILD.
Last edited by wonder (2009-04-14 20:26:39)

[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)

Error in xfce4-settings-manager When Click on Window Manager

Hello all,
I have a problem with the xfce4 environment.
First, I can't see any panel by default.
Second, the settings button near the shutdown button does not work.
Finally and more importantly, when I call from the terminal settings from terminal, settings start fine, but when I click on Window Manager or Window Manager Tweaks I get:
[jav@localhost ~]$ xfce4-settings-manager
These settings cannot work with your current window manager (GNOME Shell)
I already tried deleting sessions as mentioned in Arch wiki and also called startxfce4 again.
Any ideas?

startxfce4 should be used to start xfce4-session. It can be run from the virtual terminal(the screen-filling terminal you see when you boot up a (fresh) machine) directly or can be called in your .xinitrc. Instead of
exec xfce4-session
you should have
exec startxfce4
in your .xinitrc.
It looks like you're running startxfce4 from an X session(probably Gnome). Xfce is a replacement for Gnome, it's not run inside of Gnome or any other window manager or desktop environment(well, some parts can, like the panel). What's in your .xinitrc, especially at the exec line? Note that there should be only one exec line.
Last edited by Steef435 (2014-01-03 14:26:09)

[Solved] Systemd - Overrides settings of Gnome-Power-Manager?

Hello!
I've always used the following to lines to tell Gnome-Power-Manager not to suspend my laptop, when the lid is closed:
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank'
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
I remember a huge (and regular...) discussion around Gnome 3, because the developers resisted to re-implemented a button for this in the UI of Gnome3. Well, the two lines above done their job all the time. Since the last update of Systemd this seems to be ignored:
Oct 09 01:19:58 cupcake systemd-logind[273]: Lid closed.
Oct 09 01:19:58 cupcake systemd-logind[273]: Suspending...
Oct 09 01:19:58 cupcake systemd[1]: Starting Sleep.
Oct 09 01:19:58 cupcake systemd[1]: Reached target Sleep.
Oct 09 01:19:58 cupcake systemd[1]: Starting Suspend...
Is anyone other affected? Looks like a real problem for me. If I close the lid I want to close my lid, nothing more an especially not suspend
/var/log/pacman.log
[2012-10-08 21:59] upgraded systemd (193-1 -> 194-1)
[2012-10-08 21:59] upgraded systemd-sysvcompat (193-1 -> 194-1)
Last edited by hoschi (2012-10-08 23:53:06)

pablox wrote:
hoschi wrote:
Nope. Found it five minutes ago. My shame! Thank you
https://wiki.archlinux.org/index.php/Sy … th_systemd
This is driving me crazy. I've read the article, but I still don't understand what I'm supposed to do. I have tried changing values from logind.conf *IgnoreInhibited to yes to no, but the laptop still suspend when the lid is closed .
All you need to do is set HandleLidSwitch=ignore in logind.conf, this will make systemd ignore the lid switch completely, and leave gnome to handle it. Its pretty self explanatory... You can also set the other similar options to ignore, like HandlePowerKey, HandleSuspendKey, HandleHibernateKey if you want only gnome to handle them.
Last edited by bwat47 (2012-10-10 22:02:54)

Suggestion for dbus, hal. new gnome-volume-manager-version.

Heya,
I just installed dbus, hall from cvs and gnome-volume-manager from tarball and have some suggestions:
dbus:
the default during configure seems to be to detect if you have the necessary things installed and based on that enable a component.
To disbale qt-bindings add:
--disable-qt
to configure, else it will try to compile the qt-bindings and without a libGL.la it won't work ... (and this isn't in the Mesa package or wasn't anyway as far as I can tell).
hal:
could you add the option "--enable-fstab-sync" to configure in the new versions? It seems to be usefull . It can be it wasn't available earlier ...
gnome-volume-manager:
I just upgraded to 0.9.9 If anyone wants to have the binary just tell me where to upload.
greetz,
Michel

Michel wrote:
Heya,
I just installed dbus, hall from cvs and gnome-volume-manager from tarball and have some suggestions:
dbus:
the default during configure seems to be to detect if you have the necessary things installed and based on that enable a component.
To disbale qt-bindings add:
--disable-qt
to configure, else it will try to compile the qt-bindings and without a libGL.la it won't work ... (and this isn't in the Mesa package or wasn't anyway as far as I can tell).
there are solutions on this forum to fix the libGL.la. this file will be included with future builds of xorg/xfree86. NVIDIA drivers should also provide this file. this file is only an issue for building.
file a bug report feature report to add this build option to the package
hal:
could you add the option "--enable-fstab-sync" to configure in the new versions? It seems to be usefull . It can be it wasn't available earlier ...
if this package is in one of the three official repos file a feature request.
gnome-volume-manager:
I just upgraded to 0.9.9 If anyone wants to have the binary just tell me where to upload.
if a package has just fallen out of date up to about two week leave time for the maintainer to upgrade it . you can flage the package out of date via the web page. this is way better than offering it to people or uploading it somewhere.
the flag otu of date feature is always a better option to cluttering the list with update requests and the bug tracker is the best way to convey your wanted build changes. alot of the developers do not frequent this forum but all are member of the bug tracker notification system.

Profile Manager Error Reading Settings code:-1

Hello,
I receive this error when I am going into Profile Manager tab on server. Any ideas?
Profile Manager Error Reading Settings code:-1

Did you ever find a resolution? If not then this might help Server: An error with code -1 occurred while setting up Device Management

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)

Dbus/gnome-settings-manager error

Similar Messages

Maybe you are looking for