[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#519742: marked as done (Duplicate definitions for XF86AudioMedia in xkb/symbols/inet)



Your message dated Fri, 28 Jan 2011 04:14:36 +0100
with message-id <20110128031436.GA16853@debian.org>
and subject line Re: Bug#519742: Duplicate definitions for XF86AudioMedia in xkb/symbols/inet
has caused the Debian Bug report #519742,
regarding Duplicate definitions for XF86AudioMedia in xkb/symbols/inet
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
519742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519742
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xkb-data
Version: 1.5-2

There are two definitions for XF86AudioMedia in 
file /usr/share/X11/xkb/symbols/inet : first in "media_common" group and  
second in "nav_common" group. This both groups are included in many layouts,  
particularly in geniuscomfy2. With current version of this file 
XF86AudioMedia is broken and unusable as hotkey, other multimedia keys on my 
keyboard work normal. I fixed the problem by commenting line

key <I01>   {       [ XF86AudioMedia        ] };

in "media_common" group. 



--- End Message ---
--- Begin Message ---
Julien Cristau <jcristau@debian.org> (30/05/2009):
> How do you figure the media_common definition is the wrong one?
> Also, AFAIK two keycodes producing the same keysym is allowed, so
> this shouldn't break anything unless your clients are broken in the
> first place.  Please explain?

No reply in 1.5+ year, closing this bug.

KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: