[intrepid] bad keycode on kubuntu.xmodmap (XF86AudioLowerVolume)

Bug #284577 reported by Francisco T.
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kubuntu-default-settings (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: kubuntu-default-settings

kubuntu-default-settings:
  Installed: 1:8.10-13
  Candidate: 1:8.10-13
  Version table:
 *** 1:8.10-13 0

When I push the special Audio-stop key on my laptop, I get in xev:
 KeyPress event, serial 31, synthetic NO, window 0x3200001,
    root 0x7b, subw 0x0, time 1351189, (-1086,-55), root:(11,524),
    state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
    XKeysymToKeycode returns keycode: 122
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

But the volume-down key works fine and I get in xev:
 KeyRelease event, serial 34, synthetic NO, window 0x3200001,
    root 0x7b, subw 0x0, time 1437930, (-765,-168), root:(332,411),
    state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

In the kubuntu.xmodmap I find:
 keycode 174 = XF86AudioLowerVolume

If I comment that line, The audio-stop key shows in xev:
 KeyRelease event, serial 34, synthetic NO, window 0x2e00001,
    root 0x7b, subw 0x0, time 186665, (-773,-416), root:(324,163),
    state 0x0, keycode 174 (keysym 0x1008ff15, XF86AudioStop), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

It's seem that the keycode 174 is a problem on my laptop:

Linux portatil 2.6.27-7-generic #1 SMP Tue Oct 14 18:40:44 UTC 2008 i686 GNU/Linux
ASUSTeK Computer Inc.
F3F
1.0

Revision history for this message
gorgonizer (gorgonizer-gorgonizer) wrote :

Also observing the same issue as above, though with a different:

KeyRelease event, serial 34, synthetic NO, window 0x5800001,
    root 0x1a6, subw 0x0, time 3980942, (-276,455), root:(463,515),
    state 0x10, keycode 174 (keysym 0x1008ff15, XF86AudioStop), same_screen YES,
    XKeysymToKeycode returns keycode: 164
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

In the kubuntu.xmodmap I find:
 keycode 164 = XF86AudioStop

(I did receive exactly the same error as the poster above, but due to me having a play around it has changed, though how the new number 164 appeared, I am unsure, unless there is a newer version of the file (I reinstalled kubuntu-default-settings after changing XF86AudioStop to point to keycode 174.

Revision history for this message
alimnios72 (alimnios72) wrote :

I have the same problem in my inspiron 6000. Does anybody has an idea how to solve it?

Revision history for this message
shockdiode (shockdiode) wrote :

Hello all,
:
I ran into this same issue on my hp dv5. Here's what I did to get that button working properly:

(better safe than sorry):
sudo cp /usr/share/kubuntu-default-settings/kubuntu.xmodmap /usr/share/kubuntu-default-settings/kubuntu.xmodmap.bak

edit /usr/share/kubuntu-default-settings/kubuntu.xmodmap (as root or via sudo)

change the line in that file reading:
keycode 174 = XF86AudioLowerVolume

to read:
keycode 174 = XF86AudioStop

Save the file.

Log out/log back in to kde.

Bam, it works. Hope that helps someone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.