Error starting gnome-settings-daemon while logged in via vnc

/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
SESSION_MANAGER=local/binkleyubuntu:/tmp/.ICE-unix/4398

** (gnome-settings-daemon:4446): WARNING **: The X Server does not support the XRandR extension. Runtime resolution changes to the displa
y size are not available.

** (gnome-settings-daemon:4446): WARNING **: numlock: XkbQueryExtension returned an error

** (gnome-settings-daemon:4446): WARNING **: Neither XKeyboard not Xfree86's keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:4446): WARNING **: Unable to start a11y_keyboard manager: XKB functionality is disabled.
Xlib: extension "XInputExtension" missing on display "127.0.0.1:3.0".
Xlib: extension "XInputExtension" missing on display "127.0.0.1:3.0".
Xlib: extension "XInputExtension" missing on display "127.0.0.1:3.0".
Xlib: extension "XInputExtension" missing on display "127.0.0.1:3.0".
E: authkey.c: Failed to open cookie file '/home/lns/.pulse-cookie': Permission denied
E: authkey.c: Failed to load authorization key '/home/lns/.pulse-cookie': Invalid argument
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
Checking for Xgl: not present.
xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log
No whitelisted driver found
aborting and using fallback: /usr/bin/metacity
Window manager warning: Failed to read saved session file /home/lns/.metacity/sessions/default0.ms: Failed to open file '/home/lns/.metaci
ty/sessions/default0.ms': No such file or directory
Window manager warning: Log level 32: could not find XKB extension.
E: authkey.c: Failed to open cookie file '/home/lns/.pulse-cookie': Permission denied
E: authkey.c: Failed to load authorization key '/home/lns/.pulse-cookie': Invalid argument
Connection failure: Connection refused
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2424 error_code 3 request_code 20 minor_code 0)
  (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.)

** (gnome-settings-daemon:4519): WARNING **: The X Server does not support the XRandR extension. Runtime resolution changes to the display size are not available.

** (nm-applet:4513): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.71" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file'

** (nautilu...

I should also add that this happens with:

- A non-upgraded (Fresh Hardy) install
- A newly created user
- Manually changing theme to a non-default theme.

I've been having this as well since upgrading from Gutsy to Hardy. Same basic problem and error messages, but error info is slightly different.

~$ gnome-settings-daemon

** (gnome-settings-daemon:32689): WARNING **: The X Server does not support the XRandR extension. Runtime resolution changes to the display size are not available.

** (gnome-settings-daemon:32689): WARNING **: numlock: XkbQueryExtension returned an error

** (gnome-settings-daemon:32689): WARNING **: Neither XKeyboard not Xfree86's keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:32689): WARNING **: Unable to start a11y_keyboard manager: XKB functionality is disabled.
Xlib: extension "XInputExtension" missing on display ":1.0".
Xlib: extension "XInputExtension" missing on display ":1.0".
Xlib: extension "XInputExtension" missing on display ":1.0".
Xlib: extension "XInputExtension" missing on display ":1.0".
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
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 3728 error_code 3 request_code 20 minor_code 0)
  (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.)
~$
~$ sudo aptitude show gnome-settings-daemon
Package: gnome-settings-daemon
New: yes
State: installed
Automatically installed: no
Version: 2.22.1-0ubuntu2
Priority: extra
Section: gnome
~$
~$ lspci | grep Graphics
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
~$

Hey Marc & Jordan

I confirm. when running hardy clean installation and also disabling sound support as not needed and XRandR as well, I get quite the same output as you guys. Take a look below. I also did try to make the workaround with touching the gnome-session. nothing helped me for now.

** (gnome-settings-daemon:8997): DEBUG: Successfully connected to D-Bus
** (gnome-settings-daemon:8997): DEBUG: Starting settings manager
** (gnome-settings-daemon:8997): DEBUG: Loading settings plugins from dir: /usr/lib/gnome-settings-daemon-2.0/
(...)
** (gnome-settings-daemon:8997): DEBUG: Plugin xrandr: inactive
(...)
** (gnome-settings-daemon:8997): DEBUG: Starting sound manager
exec: 1: /usr/bin/pulseaudio: not found
** (gnome-settings-daemon:8997): DEBUG: GnomeSettingsManager: emitting plugin-activated sound
(...)
** (gnome-settings-daemon:8997): DEBUG: Activating keyboard plugin
** (gnome-settings-daemon:8997): DEBUG: Starting keyboard manager

** (gnome-settings-daemon:8997): WARNING **: numlock: XkbQueryExtension returned an error

** (gnome-settings-daemon:8997): WARNING **: Neither XKeyboard not Xfree86's keyboard extensions are available,
no way to support keyboard autorepeat rate settings
** (gnome-settings-daemon:8997): DEBUG: GnomeSettingsManager: emitting plugin-activated keyboard
** (gnome-settings-daemon:8997): DEBUG: Plugin keyboard: active
(...)
** (gnome-settings-daemon:8997): DEBUG: Starting a11y_keyboard manager

** (gnome-settings-daemon:8997): WARNING **: Unable to start a11y_keyboard manager: XKB functionality is disabled.
** (gnome-settings-daemon:8997): DEBUG: GnomeSettingsManager: emitting plugin-activated a11y-keyboard
** (gnome-settings-daemon:8997): DEBUG: Plugin a11y-keyboard: active
** (gnome-settings-daemon:8997): DEBUG: GnomeSettingsModule 0x6329e0 initialising
** (gnome-settings-daemon:8997): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libmouse.so
** (gnome-settings-daemon:8997): DEBUG: Registering GsdMousePlugin
** (gnome-settings-daemon:8997): DEBUG: Creating object of type GsdMousePlugin
** (gnome-settings-daemon:8997): DEBUG: GsdMousePlugin initializing
** (gnome-settings-daemon:8997): DEBUG: Activating mouse plugin
** (gnome-settings-daemon:8997): DEBUG: Starting mouse manager
Xlib: extension "XInputExtension" missing on display ":1.0".
Shutdown failed or nothing to shut down.
Segmentation fault

I have a similar setup as described in the original post, but simpler one: VNC over 1 Gb LAN, no SSH, vnc4server starts-up via xinetd.
The visible symptoms are exactly the same as Jordan put it, nothing to add here, and it all started after 7.1 to 8.04 upgrade.
The problem affected both upgraded machines: one is a very old 800 MHz box with 768 MB RAM, the other one is 2.4 GHz P4/1GB RAM.
Upgrading (today) the latter to 8.04.1 didn't help.
.xsession-errors is attached, in case it's of any help.

Serguei

Same problem here, after upgrading from 6.06 to 8.04.

The machine is a 2100+ rated AthlonXP with suited Board, 1GB Ram, no other fancy hardware.

I would be very happy to see a solution here, because this bug renders my setup unusable.

I'm seeing similar errors:

Common theme:
 * Upgraded from Dapper 6.06 to Hardy 8.04
 * VNC to problem box on local lan
 * xinetd to launch vnc
 * Xlib: extension "XInputExtension" missing on display ":1.0".

I'm running Kubuntu, and see this error on lots of apps, not just gnome-settings-daemon.

It seems XInputExtension is not complied into vnc4server 4.1.1 as discussed here....
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379617

This sheds a little more light on the situation, there is no XInputExtension in the free version, and it shouldn't be being asked for by the app...

http://www.realvnc.com/pipermail/vnc-list/2005-December/053489.html

Check with this
xdpyinfo | grep XInput
 (nothing)

on the physical console
xdpyinfo | grep XInput
    XInputExtension

David, FYI I upgraded from Gutsy (7.10) to Hardy, I run vnc4server via a
 WAN (over ssh tunnel), and use inetd (not xinetd) to launch vnc
sessions. So that takes 3 of 4 commonalities out of the mix.

Sincerely,
Jordan

David McNeill wrote:
> I'm seeing similar errors:
>
> Common theme:
> * Upgraded from Dapper 6.06 to Hardy 8.04
> * VNC to problem box on local lan
> * xinetd to launch vnc
> * Xlib: extension "XInputExtension" missing on display ":1.0".
>
> I'm running Kubuntu, and see this error on lots of apps, not just gnome-
> settings-daemon.
>

--
Jordan Erickson
Owner, Logical Networking Solutions
http://www.logicalnetworking.net
707-636-5678

Latest LNS Blogs - http://blogs.logicalnetworking.net

 OCZ NIA Brain -> Computer Gaming Interface
 What does it take to get a new PC with XP?
 The "laptop drive of shame"

Exact same problem, x86 and x86_64 machines: does anyone have a workaround for this missing extension? Or is there an alternative VNC server that works equally well?
-Tom

Same problem here, i have a fresh install of Ubuntu 8.04...i tried creating a new user (with fresh gnome settings) but nothing changed :o/

I experienced the same problem as many have already mentioned - namely gnome-settings-daemon fails when accessing the GNOME GUI via vnc4server.

After a little experimentation and research, I discovered what I think is a solution (or at least an easy workaround).

What works for me is to add the argument "+extension XInputExtension" to the vnc4server invocation. A most basic example would be:

vnc4server :1 +extension XInputExtension

In other words, it seems as though the XInputExtension *is* compiled into vnc4server (contrary to what some indicated), but is not activated by default. Therefore, this explicit activation of the extension resolves the issue.

So far so good, now can anyone else confirm that this works for them too?

Hi,

As well as testing the above could someone try running vnc as before,
but disabling the mouse plugin?

  gconftool-2 --set --type boolean /apps/gnome-settings-daemon/plugins/mouse/active false

The mouse plugin attempts to protect against a missing XInput extension, but
that protection may be incomplete.

Thanks,

James

  gconftool-2 --set --type boolean /apps/gnome-settings-daemon/plugins/mouse/active false

does not work.

  sudo gconftool-2 --set --type boolean /apps/gnome-settings-daemon/plugins/mouse/active false

does not work.

rebooted after both just to be sure (as I wasn't sure if the change was immediate or not).

An observation: When VNC is first launched, the theme I've chosen displays fine. When a new window is opened (say terminal or firefox or any other app), I notice the theme reverts to a default them (presumably because the settings daemon crashed?), then if the daemon successfully relaunches, I get my themed desktop back.

One surefire way to crash the daemon for good is to launch firefox and just wait. the daemon repeated crashes and the themes go back and forth about 5 or 10 times, then the dialog comes up saying the daemon crashed too many times and is disabled, after which, I have a stable (but not themed) desktop.

Hi,

Thanks for testing.

gconftool-2 --set --type boolean /apps/gnome-settings-daemon/plugins/mouse/active true

will put your system back to the way it was before.

Thanks,

James

Adding "+extension XInputExtension" to the vnc server launch doesn't work, either.

VNC version is:

# aptitude show vnc4server
Package: vnc4server
State: installed
Automatically installed: yes
Version: 4.1.1+xorg1.0.2-0ubuntu7
Priority: optional
Section: universe/x11

I use xinetd to manage the listeners. My Xvnc file for xinetd is:

service Xvnc
{
        type = UNLISTED
        disable = no
        socket_type = stream
        protocol = tcp
        wait = yes
        user = root
        server = /usr/bin/Xvnc
        server_args = -inetd :1 +extension XInputExtension -query localhost -geometry 1380x825 -depth 16 -once -fp /usr/share/fonts/X11/misc -DisconnectClients=1 -NeverShared passwordFile=/home/mwlang/.vncpasswd -extension XFIXES
        port = 5901
}

I also tried removing -extension XFIXES, but that caused me to be unable to establish a connection with the VNC desktop. Or more precisely, connection was established and immediately dropped.

Sorry everyone - my suggestion to add "+extension XInputExtension" was WRONG. It doesn't solve the issue at all. I was fooled into thinking it did because subsequent connections 'seemed' to show the correct theme indefinitely, but after a while gnome-settings-daemon failed again.

Sorry for causing unnecessary confusion!

And FYI - disabling the keyboard plugin via gconf-editor *does* appear to stop gnome-settings-daemon crashing. This is a workaround only, though. From looking at other forums/bug reports on this topic, it seems like a bug or design oversight in gnome-settings-daemon needs to be identified and resolved.

On Fri, 2008-08-01 at 01:50 +0000, level323 wrote:
> And FYI - disabling the keyboard plugin via gconf-editor *does* appear
> to stop gnome-settings-daemon crashing. This is a workaround only,
> though.

Hi,

I realise it is a workaround, but if we can have some more
confirmations that this fixes it (I realise there is one
indication that it does not as well), then it narrows down
the search.

So, can other please test disabling the mouse plugin and
report their findings please?

Thanks,

James

I went back to try the mouse disabling suggestion again. This time, I fired up gconf-editor rather than run the suggested commandline. I noticed I had both a gnome_settings_daemon and a gnome-settings-daemon. The suggested command line above uses hyphens, but the entry with underscores has the most complete set of entries, so the correct command line is probably:

 gconftool-2 --set --type boolean /apps/gnome_settings_daemon/plugins/mouse/active false

Anyway, running the daemon with mouse disabled, generates the following on the console:

mwlang@storitall:~$ gnome-settings-daemon --sync

** (gnome-settings-daemon:4295): WARNING **: The X Server does not support the XRandR extension. Runtime resolution changes to the display size are not available.

** (gnome-settings-daemon:4295): WARNING **: numlock: XkbQueryExtension returned an error

** (gnome-settings-daemon:4295): WARNING **: Neither XKeyboard not Xfree86's keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:4295): WARNING **: Unable to start a11y_keyboard manager: XKB functionality is disabled.
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

** (gnome-screensaver:4304): WARNING **: screensaver already running in this session
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 5046 error_code 3 request_code 20 minor_code 0)
  (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.)
mwlang@storitall:~$

Running:

gconftool-2 --set --type boolean /apps/gnome-settings-daemon/plugins/mouse/active false

Did *not* work for me.

I confirm this bug on a fully updated Hardy AMD64.

Disabling mouse- and keyboard-plugins seemed to solve the problem. However, i upgraded to vnc 4.1.2 after reading this:

http://ubuntuforums.org/showthread.php?t=782665

And not only did this improve the overall vnc performance greatly - gnome-settings-daemon finally seems to be happy now. Even with mouse and keyboard plugins active.

Confirm this bug on Intrepid AMD64.

SCIM doesn't work with XInputExtension failed, precisly the scim-panel-*