ANNOUNCE: xfce4-volumed 0.1.4 released

Steve Dodier sidnioulz at gmail.com
Sat Sep 5 12:29:23 CEST 2009


2009/9/5 Yves-Alexis Perez <corsac at debian.org>

> On ven, 2009-09-04 at 23:11 +0200, Steve Dodier wrote:
> > I still didn't code what's needed to allow custom keyboard shortcuts,
> > but if you mail me the keys you want i can cook you a patch for it ;)
>
> It seems the volume keys on my ThinkPad aren't detected:
>
> corsac at hidalgo: src/xfce4-volumed
> XCB: RaiseVolume ok, keycode=123 mod=0x0000
> XCB: RaiseVolume ok, keycode=123 mod=0x0000
> XCB: RaiseVolume ok, keycode=123 mod=0x0000
> XCB: LowerVolume ok, keycode=122 mod=0x0000
> XCB: LowerVolume ok, keycode=122 mod=0x0000
> XCB: LowerVolume ok, keycode=122 mod=0x0000
> XCB: Mute ok, keycode=121 mod=0x0000
> XCB: Mute ok, keycode=121 mod=0x0000
> XCB: Mute ok, keycode=121 mod=0x0000
> ** (<unknown>:20958): DEBUG: The card HDAIntelAlsamixer was found and
> set as the current card.
>
> ** (<unknown>:20958): DEBUG: There is no track label stored in xfconf
>
> ** (<unknown>:20958): DEBUG: The wanted track could not be found, using
> the first one instead.
>
> ** (<unknown>:20958): DEBUG: Xfconf volume step: 5
>
>
> And then nothing.
>
> But:
>
> corsac at hidalgo: sudo input-events 1
> /dev/input/event1
>   bustype : BUS_I8042
>   vendor  : 0x1
>   product : 0x1
>   version : 43860
>   name    : "AT Translated Set 2 keyboard"
>   phys    : "isa0060/serio0/input0"
>   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP
>
> waiting for events
> 00:22:39.554341: EV_MSC code=4 value=28
> 00:22:39.554361: EV_KEY KEY_ENTER released
> 00:22:39.554367: EV_SYN code=0 value=0
> 00:22:41.759661: EV_MSC code=4 value=176
> 00:22:41.759683: EV_KEY KEY_VOLUMEUP pressed
> 00:22:41.759690: EV_SYN code=0 value=0
> 00:22:41.903354: EV_MSC code=4 value=176
> 00:22:41.903376: EV_KEY KEY_VOLUMEUP released
> 00:22:41.903382: EV_SYN code=0 value=0
> 00:22:42.149259: EV_MSC code=4 value=174
> 00:22:42.149279: EV_KEY KEY_VOLUMEDOWN pressed
> 00:22:42.149286: EV_SYN code=0 value=0
> 00:22:42.268782: EV_MSC code=4 value=174
> 00:22:42.268805: EV_KEY KEY_VOLUMEDOWN released
>
> Hope that helps,
>
> --
> Yves-Alexis


On the application's point of view, everything is fine. It did grab
XF86AudioRaiseVolume, XF86AudioLowerVolume and XF86AudioMute. But it looks
like the keys on your keyboard aren't labelled that way. The problem is that
your keyboard is probably not correctly recognised by X (Xcb directly uses
Xlib).



2009/9/5 Brian J. Tarricone <brian at tarricone.org>

> Any particular reason you're depending on xcb-keysyms 0.3.5?  I only
> have 0.3.3 on my system (which is the latest marked stable).
>
>        -brian


When testing xvd, Lionel noticed that it wasn't working correctly on Debian
unstable, and he found out that it was because of an API change in xcb (that
of course what announced only in a commit mailing list). That change
happened on 2009-04-11, so if XCB keysyms 3.3 has been released after (i
didn't manage to find a list of tarballs for keysyms on the web), then it's
likely to work, so feel free to change the version number in
configure.acand to let me know ;)

Otherwise, I have a branch that works for older versions of xcb keysyms that
didn't have this change. I didn't upload it in git because I have no idea
how to create remote branches :) But it's available on bzr : 'bzr co
lp:~sidi/xfce4-volumed/jaunty'

SD.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.xfce.org/pipermail/xfce/attachments/20090905/16ec72c6/attachment.html>


More information about the Xfce mailing list