Bug 15783

Summary:	XF86WWW Key broken with cymotion layout
Product:	xkeyboard-config	Reporter:	Mohammed Adnène Trojette <adn>
Component:	General	Assignee:	xkb
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
URL:	http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462816
Whiteboard:
i915 platform:		i915 features:
Attachments:	fix cymotion layout

Description Mohammed Adnène Trojette 2008-04-30 17:45:48 UTC

Created attachment 16282 [details] [review]
fix cymotion layout

Hello,

here is a Debian bug report (#462816):
(patch attached)

 > From Andreas Pakulat
It seems like one of the X11 upgrades changed to produce the key code 178
for the XF86WWW key. This maps to symbol I32 and thus using the cymotion
layout I don't get my mapped action for that key anymore. The cymotion
layout currently uses I02 for XF86WWW.

 > From Michael Goth
the following patch for /usr/share/X11/xkb/symbols/inet makes all keys 
work for me. I also deleted one XF86Standby mapping which I couldn't 
produce on my keyboard.

I'm running Sid, Linux 2.6.24-1-686, xkb-data 1.1~cvs.20080104.1-1

Comment 1 Sergey V. Udaltsov 2008-05-01 01:28:20 UTC

I do not mind applying this patch. But I wonder - what was the root cause of the problem? May be, some older model used different mapping - in that case it would be better to create new model? Or any other reason?

Comment 2 Sergey V. Udaltsov 2008-12-22 16:07:40 UTC

Mohammed, could you please answer my last question? Thanks.

Comment 3 Mohammed Adnène Trojette 2008-12-22 17:04:29 UTC

(In reply to comment #2)
> Mohammed, could you please answer my last question? Thanks.

According to Andreas Pakulat, an upgrade of xkeyboard-config caused the problem. Quoting him "I can't say which upgrade exactly broke things."

Comment 4 Sergey V. Udaltsov 2008-12-24 17:21:01 UTC

Ok. Committed (updated according to the new definition of media_nav_common).

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.