Bug 486167

If the sound control isn't implemented directly in HW, you have to set the functionality at SW level. It means that you set sound volume/mute either via keyboard shortcuts or via apcid script. If you want to use acpid, the button has to generate acpi events. You can get then if you start acpid in debug mode ($ acpid -d). After you get the acpi event code, you have to write your own script. "How to" is in the documentation or take a look at working scripts /etc/acpi/*.

Anyway, this isn't bug in acpid, so I'm closing it.

I would guess that lenovo t500 is widely spread laptop among people, so it is pity that mute button does NOT work right now after normal installation.

That's not solution to write my own scripts for biggest button on keyboard from end-user's point of view.

For what component is this bug?
please change component.

bye petr :)

acpid package cannot contain this specific scripts. Every vendor has own acpi codes, so there would be a lot of scripts and only a few would be relevant for your laptop. What desktop environment do you have? Are up/down sound buttons implemented in HW or there is some SW which takes case of handling sound volume?

> Every vendor has own acpi codes, so there would be a lot of scripts and only a > few would be relevant for your laptop. 
don't care me but planty users with that lenovo t500 , I have t61 and it works there :)

> What desktop environment do you have?
It was at gnome env. Installation  was default (next>next>next) from latest fedora built, date 2009-02-18


> Are up/down sound buttons implemented in HW or there is some SW which takes
> case of handling sound volume?  
up/down works well, I don't know if there is SW|HW switch, I only now that mute button on lenovo t500 doesn't work.

........

L t500 smolt profile:
http://www.smolts.org/client/show/pub_ea607391-3e59-49f6-8a33-a9581bc5743c

(In reply to comment #4)
> > Every vendor has own acpi codes, so there would be a lot of scripts and only > > a few would be relevant for your laptop. 
> don't care me but planty users with that lenovo t500 , I have t61 and it works
> there :)

Again, t61 has HW implementation of the sound control, so on t61 buttons work out of the box without and SW requirements. In the case of t500 the situation can be different.

> > What desktop environment do you have?
> It was at gnome env. Installation  was default (next>next>next) from latest
> fedora built, date 2009-02-18

Have this installation sets any key-bindings for up/down buttons? Can you see a gnome related window with progress bar if you push a up/down sound button?

> > Are up/down sound buttons implemented in HW or there is some SW which takes
> > case of handling sound volume?  
> up/down works well, I don't know if there is SW|HW switch, I only now that mute
> button on lenovo t500 doesn't work.

As I wrote in the comment #1. Run acpid in the debug mode ($ acpid -d) and push the mute/up/down button. In the output you can see what acpi codes are generated. Then the output from debug mode past here.

>Have this installation sets any key-bindings for up/down buttons? Can you see a
>gnome related window with progress bar if you push a up/down sound button?

Yes I saw progress bar for up/down, key-bindings was set for that.

> As I wrote in the comment #1. Run acpid in the debug mode ($ acpid -d) and push
> the mute/up/down button. In the output you can see what acpi codes are
> generated. Then the output from debug mode past here.  

I haven't that machine now, ask your area-helpdesk for t500.

Seems that this issue is already reported...

*** This bug has been marked as a duplicate of bug 475247 ***