You are not logged in.
Hi, just updated system with the new linux-3.2.1
Restarted and found out that my keyboard was not in the correct layout (default QWERTY instead of fr).
But doing setxkbmap -print verbose 10 reports it good.
~ $ setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Applied rules from evdev:
rules:      evdev
model:      evdev
layout:     fr
variant:    oss
Trying to build keymap using the following components:
keycodes:   evdev+aliases(azerty)
types:      complete
compat:     complete
symbols:    pc+fr(oss)+inet(evdev)
geometry:   pc(pc104)
xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(azerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+fr(oss)+inet(evdev)"	};
	xkb_geometry  { include "pc(pc104)"	};
};Problem seams to come from detection with evdev.
Here is kernel 3.2.1 xinput list:
~ $ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech Unifying Device. Wireless PID:101b	id=8	[slave  pointer  (2)]
⎜   ↳ Logitech Unifying Device. Wireless PID:2008	id=9	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]Both keyboard and mouse are in pointer (id 8 & 9)
Old kernel 3.1.9 xinput list:
~ $ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech USB Receiver                   	id=9	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Logitech USB Receiver                   	id=8	[slave  keyboard (3)]Kernel 3.2.1 Xorg.log: http://pastebin.archlinux.fr/435307
Old Kernel 3.1.9 Xorg.log: http://pastebin.archlinux.fr/435308
EDIT:
Here is how I define my layout in /etc/X11/xorg.conf.d/10-evdev.conf:http://pastebin.archlinux.fr/435349
Temporary workaround: noticed that doing a 'setxkbmap' after X is started or at .xinitrc just make my layout ok.
Bug report to Xorg Input/Keyboard: 
https://bugs.freedesktop.org/show_bug.cgi?id=46008
Thanks
Last edited by hickop (2012-03-17 20:38:58)
Offline
never mind.
Last edited by Kodama (2012-01-19 07:30:57)
Offline
Hi,
Have you found a solution for this? I have the exact same problem with a Logitech K750.
Offline
never mind. fixed in my case through pacman -Suy.
Last edited by SammyF (2012-01-19 19:54:46)
Offline
Still can't figure out what the problem is. Probably a Xorg issue as my keyboard mapping is ok outside X. Added a temp solution, but still can't have my layout set automaticaly.
Offline
Same here!
I partially solved the problem by adding "setxkbmap fr" in .xinitrc; but the keyboard is still in qwerty upon login with SLiM.
Has anyone reported the issue?
Offline
Confirm for K360 & 3.2.0/1/2.
noticed that doing a 'setxkbmap' after X is started or at .xinitrc just make my layout ok
Thanks for workaround!
Offline

Just wondering if you had any updates on this? Just purchased a Logitech set here and I have the same issue: my azerty layout is ignored and Xorg sets it as qwerty. Loadkeys won't help, setxkbmap does.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Still the same with Linux-3.2.5-1-ARCH. I think we need to wait for xorg 1.12 and xinput 2.2.
Offline

Yep. Confirming the problem still persists with new logitech k270.
Offline
I've just updated xorg-server to 1.12 and xorg-xinput to 1.5.99 and the problem is still there... Looks like this isn't going to be solved any day soon.
Offline
Feel free to add comments to this bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=46008
Offline