I've had the same problems.  I looked in my Xorg.0.log file for how it
was describing my repeated disconnect/reconnect of my usb keyboard, and
saw mention of 'evdev' every time.

Over on
   
http://www.nabble.com/Bug-447666:-don%27t-have-the-right-xkb_layout-anymore...just-us-keyboard-td13367563.html
they describe how removing the xserver-xorg-input-evdev package (which installs 
/usr/lib/xorg/modules/input/evdev_drv.so) fixed it for them.  When I'm done 
with my other work I'll give this a shot, but wanted to share this now in case 
it might be of some help.

The entries from my log:

-- cut --
(II) config/hal: Adding input device Microsft Microsoft Wireless Optical 
Desktop? 2.20
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: always reports core 
events
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: Device: 
"/dev/input/event1"
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Found keys
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Configuring as keyboard
(II) XINPUT: Adding extended input device "Microsft Microsoft Wireless Optical 
Desktop? 2.20" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: xkb_rules: "evdev"
(**) Option "xkb_model" "pc105"
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: xkb_model: "pc105"
(**) Option "xkb_layout" "ie"
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: xkb_layout: "ie"
(II) config/hal: Adding input device Microsft Microsoft Wireless Optical 
Desktop? 2.20
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: always reports core 
events
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: Device: 
"/dev/input/event2"
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Found x and y relative 
axes
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Found x and y absolute 
axes
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Found 6 mouse buttons
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Found keys
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Configuring as mouse
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Configuring as keyboard
(II) XINPUT: Adding extended input device "Microsft Microsoft Wireless Optical 
Desktop? 2.20" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: xkb_rules: "evdev"
(**) Option "xkb_model" "pc105"
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: xkb_model: "pc105"
(**) Option "xkb_layout" "ie"
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: xkb_layout: "ie"
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: YAxisMapping: buttons 4 
and 5
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: EmulateWheelButton: 4, 
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(EE) Microsft Microsoft Wireless Optical Desktop? 2.20: Read error: No such 
device
(EE) Microsft Microsoft Wireless Optical Desktop? 2.20: Read error: No such 
device
(II) config/hal: removing device Microsft Microsoft Wireless Optical Desktop? 
2.20
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Close
(II) UnloadModule: "evdev"
(II) config/hal: removing device Microsft Microsoft Wireless Optical Desktop? 
2.20
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Close
(II) UnloadModule: "evdev"
(II) config/hal: Adding input device Microsft Microsoft Wireless Optical 
Desktop? 2.20
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: always reports core 
events
(**) Microsft Microsoft Wireless Optical Desktop? 2.20: Device: 
"/dev/input/event1"
(II) Microsft Microsoft Wireless Optical Desktop? 2.20: Found keys
... etc ...
-- cut --

I'll attach the full log as well.

Hope this helps,
B


** Changed in: gnome-control-center (Ubuntu)
       Status: Invalid => New

-- 
Keyboard layout options get lost
https://bugs.launchpad.net/bugs/305309
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to