Re: [kde-linux] [ltp] speaker/volume Problem
- From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
- Date: Fri, 1 Jun 2007 10:45:50 -0300
On Thu, 31 May 2007, Paul Kaplan wrote:
With Feisty, the Thinkpad buttons control kmix directly, not the Thinkpad
speakers. As a result, I can't turn off the Thinkpad speakers (and
They control *both* at the same time, which is *always* a very very stupid
thing to do.
This is also one of the three main reasons why I am moving the entire
nvram-key-support for thinkpads into thinkpad-acpi, and NOT generating any
events for such keys by default in anything with a hardware mixer.
Distros really should be distributing the thinkpad-aware key daemons just as
OSD and without any active actions enabled for volume up/down/mute and
brightness up/down.
How can I restore the old situation where the Thinkpad sound buttons are
controlling only the internal speakers, not kmix?
Track down thinkpad-keys, tpb, and the "thinkpad aware" crap in KDE, and
find out which ones are active in your system, and listening to volume
up/down/mute. And reconfigure them to not generate KEY_VOLUME_UP/DOWN/MUTE
events, nor DBUS events.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
___________________________________________________
This message is from the kde-linux mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
- References:
- [kde-linux] speaker/volume Problem
- From: Paul Kaplan
- [kde-linux] speaker/volume Problem
- Prev by Date: [kde-linux] left handed mouse
- Next by Date: Re: [kde] Possible to bind KDE applications to a certain IP address?
- Previous by thread: Re: [kde-linux] speaker/volume Problem
- Next by thread: Re: [kde-linux] Customized Kde
- Index(es):
Relevant Pages
|
