Re: [Halevt-dev] Exec issue

[Patrice Dumas]

On Thu, Jun 10, 2010 at 12:13:33PM +0200, Quentin Denis wrote:
> I am using 0.1.6.1 with the config file I attached. For testcase I now try to 
> bind the "mute" key (sick of getting disconnected with 'wlan'!):
> 
> address@hidden:~> lshal -m
> Start monitoring devicelist:
> -------------------------------------------------
> 12:12:31.018: computer_logicaldev_input_1 condition ButtonPressed = volume-
> down
> 12:12:32.023: computer_logicaldev_input_1 condition ButtonPressed = volume-up
> 12:12:32.836: computer_logicaldev_input_1 condition ButtonPressed = mute
> 12:12:33.434: computer_logicaldev_input_1 condition ButtonPressed = mute

I guess that you pressed successively volume-down, volume-up and mute twice?
If it is so everything looks fine.

First it would be nice if you could upgrade to 0.1.6.2. Although I doubt
that the bug is fixed, debugging support is better in 0.1.6.2 and other
bugs were fixed.

Could you then please start halevt with -d before pressing 
* first the mute key
* then another key (volume-down for example)

Then interrupt halevt and send the output to the list.

Thanks in advance.

-- 
Pat