Bug 18355

Summary:	evdev from git does weird keyboard config
Product:	xorg	Reporter:	Michael Gaber <michael.gaber>
Component:	Input/evdev	Assignee:	Peter Hutterer <peter.hutterer>
Status:	RESOLVED NOTABUG	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	medium
Version:	7.4 (2008.09)
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Michael Gaber 2008-11-02 07:11:01 UTC

i pulled evdev from git today at 13:40:29 CET to get emulateWheel working. Now i notice some strange behaviour:
1) ALT+F2 switches to second console in addition to starting the "launch" application (ALT+F* switches to console). before only CTRL+ALT*F2 would do that (and not start "launch")
2) WINDOWSKEY (Super_L) cycles through consoles and X instead of working only ad modificator.

i suspect that       
<merge key="input.xkb.rules" type="string">xorg</merge>
is not respected, since Xorg.log states 
(**) Option "xkb_rules" "evdev"
(**) AT Translated Set 2 keyboard: xkb_rules: "evdev"

Comment 1 Peter Hutterer 2008-11-02 13:48:52 UTC

On Sun, Nov 02, 2008 at 07:11:02AM -0800, bugzilla-daemon@freedesktop.org wrote:
> 1) ALT+F2 switches to second console in addition to starting the "launch"
> application (ALT+F* switches to console). before only CTRL+ALT*F2 would do that
> (and not start "launch")
> 2) WINDOWSKEY (Super_L) cycles through consoles and X instead of working only
> ad modificator.

you need to install a recent X server from git, or enable Option "GrabDevice"
"true" on each evdev device (don't do that, it's not recommended).

> i suspect that       
> <merge key="input.xkb.rules" type="string">xorg</merge>
> is not respected, since Xorg.log states 
> (**) Option "xkb_rules" "evdev"
> (**) AT Translated Set 2 keyboard: xkb_rules: "evdev"

evdev forces the evdev ruleset, and it does so for a good reason. using evdev
with ruleset xorg causes some modifier keys to stop working if a model other
than evdev is selected.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.