Bug 258083

Summary: ThinkPad A30p internal audio amplifier volume control keys always modify mixer, too
Product: [openSUSE] openSUSE 10.2 Reporter: Tobias Abt <tabt>
Component: KDEAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i586   
OS: Other   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Tobias Abt 2007-03-27 19:11:50 UTC 
On the IBM notebook ThinkPad A30p the volume up/down/mute keys are directly connected to the internal hardware audio amplifier.

Starting with openSUSE 10.2 (also in 10.3 Alpha1) if you press one of the up/down keys, the ALSA mixer master channel is also modified, which means you are "turning two knobs at the same time", which is quite annoying because it is nearly impossible to achieve a certain volume level without using the mixer app.

I would simply like to configure kmixer to ignore the keys. Clearing the global shortcut keys in the kmixer application (where the keys were initially defined) however does not help.

Using GNOME this does not occur, just with KDE. Therefore I filed it under this category.

The key codes generated when pressing those keys:
KeyRelease event, serial 28, synthetic NO, window 0x3800001,
    root 0x44, subw 0x0, time 22976313, (36,620), root:(950,1043),
    state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 31, synthetic NO, window 0x3800001,
    root 0x44, subw 0x0, time 22976989, (36,620), root:(950,1043),
    state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False
Comment 1 Cyril Hrubis 2007-03-28 13:42:23 UTC 

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