Bug#531659: [Pkg-utopia-maintainers] Bug#531659: hal-info: Audio keys in MSI Wind don't work

2010-11-30 Thread Cyril Brulebois
tag 531659 moreinfo
thanks

Hi Stefan,

Michael Biebl bi...@debian.org (20/12/2009):
 Second, if you already get X keycodes, then it is no hal/udev issue
 either afaik.

could you please tell us how it is going on an up-to-date squeeze/sid
system? It'd be nice to run the bug script to tell us a bit more about
your environment, attaching its output:
  /usr/share/bug/xorg/script 3/tmp/script.log

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#531659: [Pkg-utopia-maintainers] Bug#531659: hal-info: Audio keys in MSI Wind don't work

2009-12-19 Thread Michael Biebl
reassign 531659 xorg
thanks

Stefan Monnier wrote:
 Package: hal-info
 Version: 20090309-1
 Severity: normal
 
 [ I'm not sure how audio keys are supposed to work, so maybe this is not the
   right place to report it, but here it goes. ]
 
 When I hit the Fn-F7, Fn-F8, Fn-F9 keys (resp. volume-down, volume-up, mute)
 on my MSI Wind, nothing seems to happen.  I don't get any setkeycodes
 errors in dmesg, and instead get unmapped keycoeds in X: xev tells me
 the three keys generate the X keycodes 174, 176, and 160 (respectively).
 
 Following some hints found at
 http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-try.html,
 I tried to add a file /etc/hal/fdi/information/foo.fdi:
 
?xml version=1.0 encoding=ISO-8859-1? !-- -*- SGML -*- --
deviceinfo version=0.2
device
  !-- These are raw scancodes produced by the atkbd driver --
  match key=@input.originating_device:info.linux.driver string=atkbd
match 
 key=/org/freedesktop/Hal/devices/computer:system.hardware.vendor 
 prefix=MICRO-STAR
  match 
 key=/org/freedesktop/Hal/devices/computer:system.hardware.product 
 contains_outof=U-100
append key=input.keymap.data type=strlist00a0:mute/append
append key=input.keymap.data 
 type=strlist00ae:volumedown/append
append key=input.keymap.data 
 type=strlist00b0:volumeup/append
append key=info.capabilities 
 type=strlistinput.keymap/append
  /match
/match
  /match
/device
/deviceinfo
 
 but it didn't seem to make any difference (tho it does appear in lshal, so
 the match statements seem to work right).
 I'd love to dig deeper, but as mentioned earlier I have no idea how such
 keys are *supposed* to work, so I'd be happy to be directed to some
 info explaining how such keys are supposed to be configured.


Hi Stefan,

first of all, hal no longer does any keymap remapping (it's done by udev
nowadays), so this bug no longer belongs to hal-info.
Second, if you already get X keycodes, then it is no hal/udev issue either 
afaik.

Not entirely sure, which package to correctly reassign, so I'm using the general
xorg package. Hopefully a more knowledgeable X maintainer can help you and if
necessary reassign to a more correct package.

Cheers,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature