Bug 1882

Summary:	[XKB] (mis?)configuration yields invalid data in XGetKeyboardMapping request
Product:	xorg	Reporter:	Christophe Rhodes <csr21>
Component:	Server/General	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED MOVED	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	high
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Christophe Rhodes 2004-11-22 04:13:29 UTC

Following discussion on the portable-clx mailing list (CLX is a Common Lisp
implementation of the X client protocol) it is suspected that there is an X
server bug.  The details of the configuration in question are at
<URL:http://lists.metacircles.com/pipermail/portable-clx/2004-October/000056.html>
(I don't understand xkb, but I believe the relevant part is 'adding xkb
"type=TWO_LEVEL" for the BKSP key') and the results yield by XGetKeyboardMapping
become bogus.

This bug report may be two bugs, because the C Xlib bindings hide this problem
by calling KeyCodetoKeySym for each entry in the keyboard mapping, rather than
trusting the server's response to XGetKeyboardMapping; while this is possibly
more robust, it increases the number of server round trips.

Comment 1 Daniel Stone 2007-02-27 01:24:38 UTC

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Comment 2 chemtech 2013-03-15 14:30:26 UTC

Christophe Rhodes
Do you still experience this issue with newer soft ?
Please check the status of your issue.

Comment 3 GitLab Migration User 2018-12-13 18:34:18 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/240.

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.