[kubuntu gutsy] keyboard volume control malfunction (0-11%) on Acer laptops

Thanks for taking the time to report this bug and helping to make Ubuntu better. The correct package for this bug is hotkey-setup. From the package description hotkey-setup "will attempt to auto-detect your laptop hardware and then configure its hotkeys to produce useful keycodes. These can then be used by userspace applications."

Furter informations
In my case volume OSD remains always between 0 and 11%... with fn+up goes 11 with down 10 and so on. In any case volume doesn't change, it remains always 0 if is set to 0, 50 if 50, 80 if 80 etc.

I can confirm this bug on an Acer Aspire 5633WLMi running gutsy.

I also noticed that closing laptop lid doesn't block my screen (i have this option enabled in power manager menu of course)
I can't say if it is related to this bug.

Thanks for your bug report.

Please provide the information as described here: https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch.

My laptop is according to dmidecode an

##Acer
##Aspire 5680
##V3.01

This is the option I receive when i do sudo tail -f /var/log/acpid

dario@laptop:~$ sudo tail -f /var/log/acpid
[Mon Aug 13 18:05:16 2007] BEGIN HANDLER MESSAGES
ERROR: Couldn't attach to DCOP server!
[Mon Aug 13 18:05:17 2007] END HANDLER MESSAGES
[Mon Aug 13 18:05:17 2007] action exited with status 1
[Mon Aug 13 18:05:17 2007] executing action "/etc/acpi/actions/lm_lid.sh button/lid LID 00000080 00000002"
[Mon Aug 13 18:05:17 2007] BEGIN HANDLER MESSAGES
Laptop mode disabled, not active.
[Mon Aug 13 18:05:17 2007] END HANDLER MESSAGES
[Mon Aug 13 18:05:17 2007] action exited with status 0
[Mon Aug 13 18:05:17 2007] completed event "button/lid LID 00000080 00000002"

It seems that laptop mode is disabled?

same situation with my "logitech dinovo edge" keyboard.
OSD Volume remains always between 0% and 11% but no change can be heared.
In Addition horizontal scrolling is not possible with the Touchpad (vertical is working).

Maybe the same problem as in 118723

I have the same problem with an onboard intel 82801H HD audio controller. Maybe Kubuntu uses a switch and not the master channel with the volume control keys. But I have no idea how to change this, maybe it is even not configureable.

I have the same problem with the volume keys on gutsy, it just goes from 0 to 11%.

I tried also with newly created user, and it did not change anything.

Hardware is acer travelmate 3012wtmi

Also, closing the lid does not lock the screen, even it's set up to do so.

"OSD Volume remains always between 0% and 11% but no change can be heard.
 In Addition horizontal scrolling is not possible with the Touchpad (vertical is working)."

I have the same problem on my Lenovo 3000 V100 laptop

I have the same problem with my Laptop Acer Aspire 3100 (Volume it just goes from 0 to 11% with the Fn+Up / Fn+ Down)
So, i can confirm this... i hope this could be fixed before final Gutsy release... which is very near by now...

Cheers.

I've forgot to paste the output of dmesg which happens when i press the combination of the keys (mentioned above):

8516.032000] atkbd.c: Unknown key released (translated set 2, code 0xd9 on isa0060/serio0).
[ 8516.032000] atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.

Confirmed on my Acer Aspire 5650, which also has an HDA Intel soundcard. Note that the soundcard is working properly (although KMix chooses the speaker as default channel, but that's not such a big problem), and the Fn+up/down keys trigger the volume change OSD, it just seems to use the wrong audio channel to work with. This was working in feisty (the OSD theme was different back then).

Confirmed on Acer Aspire 5650 (HDA Intel ICH7)

Confimed for Acer Travelmate 8104WLMi (Volume just goes from 0 to 11% with the Fn+Up / Fn+ Down with no change in actual volume)

Confirmed for Zepto Znote 6014W.

Volume goes from 0% to 11%.
No output for any of the methods described in Hotkey Research.

confirmed on Toshiba Satellite A130-135 (intel 82801H HD)

Confirmed on a Acer Aspire 5044, it used to work well on Feisty.

I upgraded from Feisty, so this is not a "clean" installation. I know this shouldn't be a problem, but just saying.

Confirmed on Thinkpad X61s

Since upgrading Kubuntu form 7.04 to 7.10, the volume control exhibits the same issues as defined here in this thread. {History} With 7.04, volume worked perfectly with my keyboard volume controls... Now with the upgrading to 7.10, the volume will not increase or decrease, the OSD shown on the screen only increments to-and-from 0% - 10%.

on another note, installed Kubuntu 7.10 / with Gnome on another partition (multiple Linux boots). KDE exhibits the same issue, but Gnome seems to work fine controlling the volume via the keyboard and the OSD indicate increments form 0 thru 100%....

Seems to be an issue with KDE .....

I have the same problem with a Logitech "Access" Keyboard. The keys for "volume up" / "volume down" show "11" / "0" on the OSD but don't change the volume. Volume control by kmixer still works fine.
The "Mute Key" on the keyboard works fine too.

The problem occured after an upgrade of the motherboard on Kubuntu 7.10.
The new board supports HD Audio (HDA NVidia) but only stereo speakers are connected.

If you could use further information, don't hesitates to ask.

I have a similar (pehaps the same / related) problem:
The Fn+Up / Down keys do not change the volume.
Opening "Volume Control" and displaying all the options I found these keys are now controling the "capture" ("Captura" in Portuguese) level, in the "Recording" tab.

ACER Aspire 5102 WLMi
Ubuntu 8.1

My case is solved, thanks to:
http://coolarm.wordpress.com/2008/06/15/keyboard-volume-control-ubuntu-not-working/
Probably I mixed the sound preferences trying to get my mike to work...

Since this problem has only been reported against Kubuntu, I presume that it's a problem with some KDE component - I'm not sure which one, so reassigning to kubuntu-meta.

Still a problem in 9.04 or 9.10?

KMilo (which is no longer maintained) handled this back in the day. Any further issues of this nature should have a separate report, imo, since the software stack is completely different and using an old report would just confuse things.

Closing as won't fix due to KMilo being unmaintained by KDE.