Package: xbindkeys Version: 1.8.2-1 Severity: normal XBindkeys seems to be dropping certain keycodes when they are added to ~/.xbindkeysrc.
I have a laptop with special media keys (play, stop, volume up/down, mute, etc) and nearly all of these play nice with xbindkeys, except for the mute key. When I do not have a line in .xbindkeysrc handling this key (Mute, keycode 160) I can get events from xbindkeys -k or xev or the like, so I know that the key itself works. However, when I add a line to .xbindkeysrc # Mute "amixer set PCM toggle" m:0x0 + c:160 as xbindkeys -k reports, xbindkeys seems to quietly drop the event, as it doesn't execute the command, or allow xbindkeys -r or xev to see the events occur. Other than this, xbindkeys is working fantasticly, even with most of the buttons on my logitech mx610 mouse (all except the mute key, which also generates keycode 160 under the above circumstances) -- System Information: Debian Release: lenny APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xbindkeys depends on: ii guile-1.6-libs 1.6.8-6 Main Guile libraries ii libc6 2.7-10 GNU C Library: Shared libraries ii libguile-ltdl-1 1.6.8-6 Guile's patched version of libtool ii libqthreads-12 1.6.8-6 QuickThreads library for Guile ii libx11-6 2:1.0.3-7 X11 client-side library xbindkeys recommends no packages. -- no debconf information
