Re: [Halevt-dev] Exec issue

[Quentin Denis]

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


address@hidden:~> halevt -i
Condition: 
/org/freedesktop/Hal/devices/computer_logicaldev_input_1,ButtonPressed 
(volume-up)
Condition: 
/org/freedesktop/Hal/devices/computer_logicaldev_input_1,ButtonPressed 
(volume-down)
Condition: 
/org/freedesktop/Hal/devices/computer_logicaldev_input_1,ButtonPressed (mute)
Condition: 
/org/freedesktop/Hal/devices/computer_logicaldev_input_1,ButtonPressed (mute)


The same happens, any keystroke (mute, volume up, volume down, and many 
others) trigger the same event (here: xterm defined in my config)

Thanks and kind regards,
Quentin

On Wednesday 09 June 2010 21:30:41 Patrice Dumas wrote:
> On Wed, Jun 09, 2010 at 08:51:10PM +0200, Quentin Denis wrote:
> > Hello everyone,
> > 
> > I just tested halevt on my openSUSE box and I get a severe issue. I don't
> > know if it is a bug or a misconfiguration, but halevt will exec my
> > command everytime any function key is pressed. This means that my "wlan"
> > key is not recognized correctly since I get the same reaction to my
> > "mute" or any other multimedia key.
> > 
> > I just want to have my "wlan" keycode mapped to execute an application.
> > My config file is attached to this email.
> 
> What version of halevt are you using? Match on Halevt:Condition appeared
> in 0.1.5.
> 
> Also maybe hal is not passing the information. You can start
>  lshal -m
> before you push the button.
> 
> Another possibility is that halevt doesn't see the even. It may be checked
> by starting
>  halevt -i
> before pushing the button.

halevt.xml
Description: application/xml