Your message dated Fri, 25 Feb 2011 22:15:42 +0100
with message-id <[email protected]>
and subject line Re: Bug#531659: [Pkg-utopia-maintainers] Bug#531659: hal-info:
Audio keys in MSI Wind don't work
has caused the Debian Bug report #531659,
regarding hal-info: Audio keys in MSI Wind don't work
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 [email protected]
immediately.)
--
531659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531659
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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="strlist">00a0:mute</append>
<append key="input.keymap.data"
type="strlist">00ae:volumedown</append>
<append key="input.keymap.data" type="strlist">00b0:volumeup</append>
<append key="info.capabilities" type="strlist">input.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.
Stefan
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500,
'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
Cyril Brulebois <[email protected]> (30/11/2010):
> 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
no reply in a while, closing this bug accordingly.
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
