Bug 132567 - "Volume up" key (XF86AudioRaiseVolume) is not working anymore
Summary: "Volume up" key (XF86AudioRaiseVolume) is not working anymore
Status: RESOLVED NOT A BUG
Alias: None
Product: kmilo
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: George Staikos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-17 21:35 UTC by Dima Ryazanov
Modified: 2006-09-01 12:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dima Ryazanov 2006-08-17 21:35:49 UTC
Version:            (using KDE KDE 3.5.4)
Installed from:    Gentoo Packages
Compiler:          gcc version 4.1.1 (Gentoo 4.1.1) 
OS:                Linux

Before, with KDE 3.5.3 (I think), the volume keys on my keyboard worked perfectly.

Now, I reinstalled everything and upgraded to KDE 3.5.4, and I cannot increase the volume anymore. The "volume up" key has no effect. The "volume down" and "mute" keys still work as expected.


I tried running xev, and pressed "volume up", then "volume down". It displays everything correctly:

KeyPress event, serial 32, synthetic NO, window 0x2600001,
    root 0x4c, subw 0x0, time 496840893, (394,37), root:(398,782),
    state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XKeysymToKeycode returns keycode: 175
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 32, synthetic NO, window 0x2600001,
    root 0x4c, subw 0x0, time 496841109, (394,37), root:(398,782),
    state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XKeysymToKeycode returns keycode: 175
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

FocusOut event, serial 32, synthetic NO, window 0x2600001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 32, synthetic NO, window 0x2600001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 32, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
           0   0   0   0   0   64  0   0   0   0   0   0   0   0   0   0

KeyRelease event, serial 32, synthetic NO, window 0x2600001,
    root 0x4c, subw 0x0, time 496841765, (394,37), root:(398,782),
    state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False


Looks like it never received the "KeyPress" for "XF86AudioLowerVolume" - I assume it's because it was intercepted by KMilo.


Just to be sure it wasn't some configuration problem, I tried it with a different user with no KDE settings - and got the same result.
Comment 1 Carsten Lohrke 2006-08-18 02:53:26 UTC
Does it, when you add the line

keycode 175 = XF86AudioLowerVolume

to 

/etc/X11/Xmodmap

and restart X?
Comment 2 Dima Ryazanov 2006-08-18 03:13:15 UTC
I didn't have that file, so I created it, with just that like. But it didn't make any difference.

Also, why XF86AudioLowerVolume not XF86AudioRaiseVolume? And, the keycode 175 is already mapped to XF86AudioRaiseVolume - at least, that's what xev shows.
Comment 3 Will Stephenson 2006-08-31 17:33:57 UTC
I can reproduce this on SUSE 10.1 as well.  Since I can reproduce with a simple Xlib test case, I don't think it's a KDE bug.  

See https://bugzilla.novell.com/show_bug.cgi?id=200685 for details.
Comment 4 Lubos Lunak 2006-09-01 12:34:52 UTC
Right, not a KDE bug.