[hardy] The Settings Daemon restarted too many times.

Not sure this is a duplicate, in my case it doesn't seem to be crashing.

what videocard and driver are you using?

On Mon, Mar 03, 2008 at 06:04:06PM -0000, Sebastien Bacher wrote:
> what videocard and driver are you using?

As posted in

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/197153/comments/19

I'm using the nvidia driver. The card is:
01:00.0 VGA compatible controller: nVidia Corporation NV36GL [Quadro FX 1100] (rev a1)

Ryan

Sebastien Bacher wrote:
> *** This bug is a duplicate of bug 197153 ***
> https://bugs.launchpad.net/bugs/197153
>
> what videocard and driver are you using?
>
>
Hi Sebastien,

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM
Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated
Graphics Device (rev 02)

Attached copy of Xorg.conf

Cheers,

Phil

# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "us"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizScrollDelta" "0"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "stylus"
 Option "Device" "/dev/input/wacom"
 Option "Type" "stylus"
 Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "eraser"
 Option "Device" "/dev/input/wacom"
 Option "Type" "eraser"
 Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "cursor"
 Option "Device" "/dev/input/wacom"
 Option "Type" "cursor"
 Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "Device"
 Identifier "Intel Corporation 82852/855GM Integrated Graphics Device"
 Boardname "i810"
 Busid "PCI:0:2:0"
 Driver "i810"
 Screen 0
EndSection

Section "Monitor"
 Identifier "Generic Monitor"
 Vendorname "Generic LCD Display"
 Modelname "LCD Panel 1024x768"
 Horizsync 31.5-48.5
 Vertrefresh 40-70
  modeline "640x480@60" 25.2 640 656 752 800 480 490 492 525 -vsync -hsync
  modeline "800x600@56" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
  modeline "800x600@60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
  modeline "1024x768@60" 65.0 1024 1048 1184 1344 768 771 777 806 -vsync -hsync
 Gamma 1.0
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "Intel Corporation 82852/855GM Integrated Graphics Device"
 Monitor "Generic Monitor"
 Defaultdepth 24
 SubSection "Display"
  Depth 24
  Virtual 1024 768
  Modes "1024x768@60" "800x600@60" "800x600@56" "640x480@60"
 EndSubSection
EndSection

Se...

I am running a system that was upgraded from Gutsy to Hardy and updated a week ago (mid-May 2008) and am seeing this too. Wasn't a problem with Gutsy. I agree with the posters in this thread and that thread - this doesn't seems like a duplicate - can we get this unmarked and reopened, or should I open a new bug?

I'm seeing the error mentioned in the headline when I vnc into my server (which runs Xfce). When I execute manually, no crash, just erroring out:

~$ 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)
~$

I can attach xorg.conf if someone reopens this bug.

Thanks,

   Marc

Never mind. Someone else opened Bug #239342 which describes my exact problem. Now if we can find a resolution...