After instalation of Kubuntu 7.10 on Acer Extensa 5513NWLMi, the control ou sound volume using jey shortcut Fn + arrow up/down (Acer standart, Acer Aspire with Kubuntu 7.04 it worked automatically without any problem).

[Vojta]

After instalation of Kubuntu 7.10 on Acer Extensa 5513NWLMi I cannot use keyboart shortcut to control sound volume. Normaly, Acer use Fn + arrow up or down (this has been working since install without any problem on Acer Aspire 3692NWLMi). When I use keyboard shortcut, values are oscilating between O and 11 % without any effect on real sound volume. Mutting (Fn + F8) works. KMix is set to PCM and using mouse with icon in panel works.

[Carlos Cáceres (betomadrid)]

I can confirm the same bug, in kubuntu 7.04 with a little work i could configure the sound system without any complication but when i upgrade my system to Gutsy the shortcut of my keyboard that control the volume stop work, and only moves between 0 and 11% whitout any diference in the level of volume.... My computer isn't an Acer Extensa is a desktop.

[Vojta (vojta-sc-deactivatedaccount-deactivatedaccount)]

Hello, I solved the problem in this way: I downgraded kmilo package to the version from Kubuntu 7.04 and keyboard volume control started work again, so that there is the bug in kmilo package. No, I try to fix the package to not be upgraded to functionless version.

[Erich Jansen (erichjansen-deactivatedaccount)]

I can confirm this bug on Acer Aspire 5610z. Trying to adjust the volume only allows you to go as high as 11% with no change to the actual volume.

[FrozenPenguin (prome1-mail)]

Same here on Acer Aspire 561ANWLMi.

[Zorael (zorael)]

Duplicate of https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/118723

See socketbind's comment at that bug for a patched Gutsy .deb; https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/118723/comments/34

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!