gnome-settings-daemon not starting with 1:2.19.92-0ubuntu3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
xserver-xorg-input-synaptics (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gnome-control-
after upgrading to 1:2.19.92-0ubuntu3 I got the " gnome settings daemon could not be started" dialog on login and all my theme and fonts were broken.
I downgraded the gnome-control-
The gnome-settings-
The program 'gnome-
This probably reflects a bug in the program.
The error was 'BadDevice, invalid or uninitialized input device'.
(Details: serial 666 error_code 171 request_code 147 minor_code 3)
(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.)
[1190050552,
Matthew Garrett (mjg59) wrote : | #1 |
Changed in gnome-control-center: | |
status: | New → Fix Released |
tduermeier (tduermeier) wrote : | #2 |
I ran into this same problem this morning when I updated my synaptics driver. I'm running on Gutsy on a Dell inspiron e1405. Uninstalling the xserver-
lockey (thomasjlocke) wrote : | #3 |
I have the same problem. Uninstalling xserver-
xserver-
Version 0.14.6-0ubuntu8
Linux 2.6.22-11-generic
Cameron Harris (cameronh) wrote : | #4 |
I'm having the same problem, and disabling the synaptics driver also fixed it. I've just now update/
$ gnome-settings-
[...]
The error was 'BadDevice, invalid or uninitialized input device'.
(Details: serial 1395 error_code 171 request_code 151 minor_code 3)
[...]
nick (kcin1204) wrote : Re: [Bug 140485] Re: gnome-settings-daemon not starting with 1:2.19.92-0ubuntu3 | #5 |
not to sound dumb or anything but how do you disable the synaptic
driver? also i dont quiet understand did you say that it helped or it
didn't?
nick
On 9/17/07, thecwin <email address hidden> wrote:
> I'm having the same problem, and disabling the synaptics driver also
> fixed it. I've just now update/
>
> $ gnome-settings-
> [...]
> The error was 'BadDevice, invalid or uninitialized input device'.
> (Details: serial 1395 error_code 171 request_code 151 minor_code 3)
> [...]
>
> --
> gnome-settings-
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
nick (kcin1204) wrote : | #6 |
ohh i just looked it up.... if im reading correctly disabling the
synaptic driver would disable my touchpad. i cant do that as i need
it.... keep in contact and let me know if you find a fix and ill do
the same...
thanks
nick
On 9/17/07, thecwin <email address hidden> wrote:
> I'm having the same problem, and disabling the synaptics driver also
> fixed it. I've just now update/
>
> $ gnome-settings-
> [...]
> The error was 'BadDevice, invalid or uninitialized input device'.
> (Details: serial 1395 error_code 171 request_code 151 minor_code 3)
> [...]
>
> --
> gnome-settings-
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
nick (kcin1204) wrote : | #7 |
sorry for all the emails.... it looks as though it got fixed when i
did a sudo apt-get update/upgrade. but im not sure if it was that or
when i also installed another package called gsynaptics. But the
problem is that now ive lost my scrolling functionality and my
terminal wont open up right. what about you?
nick
On 9/17/07, thecwin <email address hidden> wrote:
> I'm having the same problem, and disabling the synaptics driver also
> fixed it. I've just now update/
>
> $ gnome-settings-
> [...]
> The error was 'BadDevice, invalid or uninitialized input device'.
> (Details: serial 1395 error_code 171 request_code 151 minor_code 3)
> [...]
>
> --
> gnome-settings-
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
riahmatic (riahmatic) wrote : | #8 |
The latest update has resolved this problem for me.
tduermeier (tduermeier) wrote : | #9 |
The latest update did fix my problem for gnome-settings-
TD
nick (kcin1204) wrote : Re: [Bug 140485] Re: gnome-settings-daemon not starting with 1:2.19.92-0ubuntu3 | #10 |
tduermeier wrote:
> The latest update did fix my problem for gnome-settings-
> even though I have reinstalled the xorg driver my scrolling function is
> totally lost from my touchpad. I've tried dpkg-reconfigure xserver-xorg
> and set up the touchpad the same as I always had it before, but still no
> go. I have gsynaptics and libsynaptics0 installed and have enabled
> horizontal and vertical scrolling, but no difference. I made sure to
> add "Option" "SHMConfig" "On" to my xorg.conf, but still no results. I
> just tried reinstalling the xorg driver, but that also did not work. If
> anyone has any tips regarding getting the scroll functionality back
> after removing the xorg driver I would very much appreciate it.
>
> TD
>
>
go to system-
settings there you'll see them...
nick
tduermeier (tduermeier) wrote : Re: [Bug 140485] Re: gnome-settings-daemon not starting with 1:2.19.92-0ubuntu3 | #11 |
Boy do I feel thick-headed :)
I was so caught up in the synaptics driver I didn't even bother to look
there. Thanks aplenty, problem solved!
-TD
On 9/18/07, nick <email address hidden> wrote:
>
> tduermeier wrote:
> > The latest update did fix my problem for gnome-settings-
> > even though I have reinstalled the xorg driver my scrolling function is
> > totally lost from my touchpad. I've tried dpkg-reconfigure xserver-xorg
> > and set up the touchpad the same as I always had it before, but still no
> > go. I have gsynaptics and libsynaptics0 installed and have enabled
> > horizontal and vertical scrolling, but no difference. I made sure to
> > add "Option" "SHMConfig" "On" to my xorg.conf, but still no results. I
> > just tried reinstalling the xorg driver, but that also did not work. If
> > anyone has any tips regarding getting the scroll functionality back
> > after removing the xorg driver I would very much appreciate it.
> >
> > TD
> >
> >
> go to system-
> settings there you'll see them...
> nick
>
> --
> gnome-settings-
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
michelem (michele-marcucci) wrote : | #12 |
Tristan Tarrant (tristan-tarrant) wrote : | #13 |
Doesn't work for me either using xserver-
Cameron Harris (cameronh) wrote : | #14 |
Problem remains for me, using xserver-
Rich (rincebrain) wrote : | #15 |
Problem also remains for me - xserver-
Rich (rincebrain) wrote : | #16 |
The "fix" didn't fix it for a number of people, myself included.
Changed in xserver-xorg-input-synaptics: | |
status: | Fix Released → In Progress |
Pavel Rojtberg (rojtberg) wrote : | #17 |
still got the error; I am using synaptics and evdev for my pointers.
As a workaround I recompiled the cntrol-center without the touchpad patches.
If theres intrest I can share the packages...
Changed in xserver-xorg-input-synaptics: | |
importance: | Undecided → Medium |
Cameron Harris (cameronh) wrote : | #18 |
Considering Pavel Rojtberg managed to fix this by recompiling control-center, doesn't this indicate that at least some bug may lie in the control-center package? Would I be correct in stating that an X client, particularly one as important as the gnome-control-
Should we update this to say that it affects both the synaptics driver and control-center?
michelem (michele-marcucci) wrote : | #19 |
Today I upgrade my Gutsy and the problem persists, I cannot lunch the gnome-setting-
m1k@goa:~$ gnome-settings-
The program 'gnome-
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 751 error_code 2 request_code 147 minor_code 35)
(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.)
[1190288354,
I downgraded the package libgnome-
André Sencioles (andre-sencioles) wrote : | #20 |
- $strace gnome-settings-daemon Edit (36.9 KiB, application/octet-stream)
I have the same issue here. Also using xserver-
I'm going to upload the trace from the gnome-settings-
Here follows the output:
The program 'gnome-
This probably reflects a bug in the program.
The error was 'BadDevice, invalid or uninitialized input device'.
(Details: serial 1551 error_code 171 request_code 147 minor_code 3)
(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.)
[1190291224,
Some info on the package versions:
ii gnome-control-
ii xserver-
My source.list:
# Ubuntu Gutsy
deb http://
deb http://
deb http://
deb http://
Matthew Garrett (mjg59) wrote : | #21 |
Do those of you having this problem have touchpads on your machines?
Tobias Wolf (towolf) wrote : | #22 |
Yes. And it's persisting here too.
André Sencioles (andre-sencioles) wrote : | #23 |
I have a touchpad using synaptics driver too.
Another user reported that gnome-settings-
I'll test it later today and will update if it works.
André Sencioles (andre-sencioles) wrote : | #24 |
I've just confirmed that disabling the synaptics driver allows gnome-settings-
michelem (michele-marcucci) wrote : | #25 |
I have a synaptic touchpad too but I didn't test disabling it yet
Tobias Wolf (towolf) wrote : | #26 |
I have some gdb output for this:
Breakpoint 2, gdk_x_error (display=0x808f100, error=0xbfec99d8)
at /build/
614 /build/
in /build/
(gdb) bt
#0 gdk_x_error (display=0x808f100, error=0xbfec99d8)
at /build/
#1 0xb7168655 in bonobo_
at bonobo-ui-main.c:58
#2 0xb7f59f50 in xkl_process_error () from /usr/lib/
#3 0xb7849c4a in _XError (dpy=0x808f100, rep=0xbfec9aac)
at ../../src/
#4 0xb784b714 in _XReply (dpy=0x808f100, rep=0xbfec9aac, extra=0, discard=0)
at ../../src/
#5 0xb7902b32 in XOpenDevice (dpy=0x808f100, id=1) at ../../src/
#6 0x0805dcbb in set_tap_to_click (state=<value optimized out>)
at gnome-settings-
#7 0x0805ddb8 in gnome_settings_
at gnome-settings-
#8 0x0805cd2d in gnome_settings_
at gnome-settings-
#9 0x08058923 in start_modules (daemon=<value optimized out>,
runlevel=
at gnome-settings-
#10 0x08058983 in start_modules_
at gnome-settings-
#11 0xb769a551 in g_idle_dispatch (source=0x80c2f10, callback=
user_
---Type <return> to continue, or q <return> to quit---
#12 0xb769c11c in IA__g_main_
at /build/
#13 0xb769f55f in g_main_
dispatch=1, self=0x8074470)
at /build/
#14 0xb769f909 in IA__g_main_loop_run (loop=0x80adc98)
at /build/
#15 0xb7bd29e4 in IA__gtk_main ()
at /build/
#16 0x08055bd4 in main (argc=0, argv=0x8087810) at factory.c:48
(gdb) q
Tobias Wolf (towolf) wrote : | #27 |
(gdb) thread apply all bt full
Thread 2 (Thread -1228780656 (LWP 6800)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb76501fb in ?? () from /lib/tls/
No symbol table info available.
#2 0xb76b00bd in child_watch_
at /build/
b = "B�d��C¶
list = (GSList *) 0xb764cc80
#3 0xb76d25af in g_thread_
at /build/
#4 0xb764946b in start_thread () from /lib/tls/
No symbol table info available.
#5 0xb75cc6be in clone () from /lib/tls/
No symbol table info available.
Thread 1 (Thread -1227261632 (LWP 6796)):
#0 gdk_x_error (display=0x808f100, error=0xbffe3ae8)
at /build/
No locals.
#1 0xb717b655 in bonobo_
---Type <return> to continue, or q <return> to quit---
at bonobo-ui-main.c:58
No locals.
#2 0xb7f6cf50 in xkl_process_error () from /usr/lib/
No symbol table info available.
#3 0xb785cc4a in _XError (dpy=0x808f100, rep=0xbffe3bbc)
at ../../src/
rtn_val = <value optimized out>
event = {type = 0, xany = {type = 0, serial = 134803712,
send_event = 0, display = 0x9fd, window = 3070465451}, xkey = {type = 0,
serial = 134803712, send_event = 0, display = 0x9fd, window = 3070465451,
root = 3078781164, subwindow = 3080254792, time = 3221109568,
x = -1208185229, y = -1214712064, x_root = 0, y_root = 1, state = 1,
keycode = 0, same_screen = -1216171644}, xbutton = {type = 0,
serial = 134803712, send_event = 0, display = 0x9fd, window = 3070465451,
root = 3078781164, subwindow = 3080254792, time = 3221109568,
x = -1208185229, y = -1214712064, x_root = 0, y_root = 1, state = 1,
button = 0, same_screen = -1216171644}, xmotion = {type = 0,
serial = 134803712, send_event = 0, display = 0x9fd, window = 3070465451,
root = 3078781164, subwindow = 3080254792, time = 3221109568,
x = -1208185229, y = -1214712064, x_root = 0, y_root = 1, state = 1,
is_hint = 0 '\0', same_screen = -1216171644}, xcrossing = {type = 0,
serial = 134803712, send_event = 0, display = 0x9fd, window = 3070465451,
root = 3078781164, subwindow = 3080254792, time = 3221109568,
---Type <return> to continue, or q <return> to quit---
x = -1208185229, y = -1214712064, x_root = 0, y_root = 1, mode = 1,
detail = 0, same_screen = -1216171644, focus = 689, state = 3078750208},
xfocus = {type = 0, serial = 134803712, send_event = 0, display = 0x9fd,
window = 3070465451, mode = -1216186132, detail = -1214712504}, xexpose = {
type = 0, serial = 134803712, send_event = 0, display = 0x9fd,
window = 3070465451, x = -1216186132, y = -1214712504,
width = -1073857728, height = -1208185229, count = -1214712064},
xgraphicsexpose = {type = 0, serial = 134803712, send_event = 0,
display = 0x9fd, drawable = 30704...
Tobias Wolf (towolf) wrote : | #28 |
and finally my xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Samsung"
InputDevice "Synaptics Touchpad"
InputDevice "MS Intellimouse"
EndSection
Section "Files"
RgbPath "/usr/lib/X11/rgb"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Samsung"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"
EndSection
#Section "InputDevice"
# Identifier "Samsung"
# Driver "evdev"
# Option "Device" "/dev/input/event1"
# Option "Name" "AT Translated Set 2 keyboard"
# Option "CoreKeyboard"
# Option "XkbRules" "base"
# Option "XkbModel" "evdev"
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#EndSection
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "CorePointer"
Option "SendCoreEvents" " true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
# Option "HorizScrollDelta" "100"
# Option "VertScrollDelta" "100"
# Option "AlwaysCore"
# Option "Buttons" "7"
# Option "LeftEdge" "1700"
# Option "RightEdge" "5300"
# Option "TopEdge" "1700"
# Option "BottomEdge" "4200"
# Option "FingerLow" "25"
# Option "FingerHigh" "30"
# Option "MaxTapTime" "180"
# Option "MaxTapMove" "220"
# Option "MinSpeed" "0.12"
# Option "MaxSpeed" "0.20"
# Option "AccelFactor" "0.0010"
# Option "SHMConfig" "on"
EndSection
Section "InputDevice"
Identifier "MS Intellimouse"
Driver "evdev"
#Option "CorePointer"
Option "Device" "/dev/input/event9"
Option "Name" "*IntelliMouse*"
Option "SendCoreEvents"
Option "Buttons" "9"
Option "ZAxisMapping" "4 5 6 7"
Option "Resolution" "800"
EndSection
Section "Monitor"
Identifier "S30 Digital Panel"
VendorName "Samsung"
ModelName "CRT-0"
DisplaySize 444 277
HorizSync 31.0 - 90.0
VertRefresh 59.0 - 85.0
Option "DPMS"
EndSection
Section "Device"
Identifier "NVIDIA Corporation NV34M [GeForce FX Go5200 32M/64M]"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce FX Go5200 32M/64M"
EndSection
Section "Screen"
Identifier "Screen0"
Device "NVIDIA Corporation NV34M [GeForce FX Go5200 32M/64M]"
Monitor "S30 Digital Panel"
DefaultDepth 24
Option "Coolbits" "1"
Option "NvAGP" "1"
...
Matthew Garrett (mjg59) wrote : | #29 |
Ok, there seem to be two issues here. One involves a BadDevice error, the other a BadValue. Could people please confirm which it is that they're seeing?
Keenan Pepper (keenanpepper) wrote : | #30 |
I'm getting BadDevice with gnome-control-
keenan@
Warning: No symbols defined for <SYRQ> (keycode 92)
Warning: No symbols defined for <II65> (keycode 101)
Warning: No symbols defined for <BRK> (keycode 114)
Warning: No symbols defined for <FK13> (keycode 118)
Warning: No symbols defined for <FK14> (keycode 119)
Warning: No symbols defined for <FK15> (keycode 120)
Warning: No symbols defined for <FK16> (keycode 121)
Warning: No symbols defined for <FK17> (keycode 122)
Warning: No symbols defined for <KPDC> (keycode 123)
Warning: No symbols defined for <XFER> (keycode 129)
Warning: No symbols defined for <I02> (keycode 130)
Warning: No symbols defined for <NFER> (keycode 131)
Warning: No symbols defined for <I04> (keycode 132)
Warning: No symbols defined for <AE13> (keycode 133)
Warning: No symbols defined for <I06> (keycode 134)
Warning: No symbols defined for <I07> (keycode 135)
Warning: No symbols defined for <I08> (keycode 136)
Warning: No symbols defined for <I09> (keycode 137)
Warning: No symbols defined for <I0A> (keycode 138)
Warning: No symbols defined for <I0B> (keycode 139)
Warning: No symbols defined for <I0C> (keycode 140)
Warning: No symbols defined for <I0D> (keycode 141)
Warning: No symbols defined for <I0E> (keycode 142)
Warning: No symbols defined for <I0F> (keycode 143)
Warning: No symbols defined for <I10> (keycode 144)
Warning: No symbols defined for <I11> (keycode 145)
Warning: No symbols defined for <I12> (keycode 146)
Warning: No symbols defined for <I13> (keycode 147)
Warning: No symbols defined for <I14> (keycode 148)
Warning: No symbols defined for <I15> (keycode 149)
Warning: No symbols defined for <I16> (keycode 150)
Warning: No symbols defined for <I17> (keycode 151)
Warning: No symbols defined for <I18> (keycode 152)
Warning: No symbols defined for <I19> (keycode 153)
Warning: No symbols defined for <I1A> (keycode 154)
Warning: No symbols defined for <I1B> (keycode 155)
Warning: No symbols defined for <K59> (keycode 157)
Warning: No symbols defined for <I1E> (keycode 158)
Warning: No symbols defined for <I1F> (keycode 159)
Warning: No symbols defined for <I20> (keycode 160)
Warning: No symbols defined for <I21> (keycode 161)
Warning: No symbols defined for <I22> (keycode 162)
Warning: No symbols defined for <I23> (keycode 163)
Warning: No symbols defined for <I24> (keycode 164)
Warning: No symbols defined for <I25> (keycode 165)
Warning: No symbols defined for <I26> (keycode 166)
Warning: No symbols defined for <I27> (keycode 167)
Warning: No symbols defined for <I28> (keycode 168)
Warning: No symbols defined for <I29> (keycode 169)
Warning: No symbols de...
Cameron Harris (cameronh) wrote : | #31 |
People who are getting BadValue might want to check out bug #140469 - It seems unrelated to the bug we are discussing here which is BadDevice when using synaptics touchpad.
Matthew Garrett (mjg59) wrote : | #32 |
Ah. Try removing the
Option "CorePointer"
line from the synaptics configuration. This currently confuses things. I'll look into that now.
Matthew Garrett (mjg59) wrote : | #33 |
Ok, got it. There's no way to make the new-style configuration work if you've configured the synaptics pad as your core pointer device, so I'm fixing it such that it makes things no worse than they were before. You won't be able to use the new control panel, but your old configuration will work as it did before.
Matthew Garrett (mjg59) wrote : | #34 |
2.20.0-0ubuntu2 should fix this. Please note that the touchpad preferences will not appear with your configuration - if you specify Option CorePointer, the method we use to alter the touchpad settings cannot work. This will change in a future version of the X server, but not in time for gutsy. In any case, this will restore the behaviour back to the way it was previously for you. Removing that option should allow you to perform runtime configuration.
Changed in xserver-xorg-input-synaptics: | |
status: | In Progress → Invalid |
Changed in gnome-control-center: | |
status: | New → Fix Released |
Dana Goyette (danagoyette) wrote : | #35 |
I've always used gsynaptics, anyway.... the new panel is nearly useless, because it is too basic -- it doesn't even have sensitivity adjustments, for example.
I think SHMConfig should be enabled by default, and gsynaptics installed with it. At least that works with touchpad as CorePointer. I had to build my own package with the two relevant patches removed, also, to get my g-s-d back.
The new version of the synaptics driver just uploaded ought to fix this - please reopen if it doesn'