You are not logged in.

Pages: 1

#1 2019-02-18 11:34:59

josemota
Member
Registered: 2010-10-24
Posts: 47

Volume keys not being recognized

Hello,

When I attempt to use any of three volume keys (up keycode 115 / down keycode 114 / mute keycode 113), they are not recognized.

Here's some data that might help, let me know if you need any more input from me, I'll gladly comply:

* i3-gaps 4.16.1-1
* linux 4.20.8.arch1-1
* xorg-server 1.20.3-1

Output from xev

##  \ \     /       |                                |
##   \ \   /  _ \   |  |   |  __ `__ \    _ \     _` |   _ \ \ \  \   /  __ \
##    \ \ /  (   |  |  |   |  |   |   |   __/    (   |  (   | \ \  \ /   |   |
##     \_/  \___/  _| \__,_| _|  _|  _| \___|   \__,_| \___/   \_/\_/   _|  _|

FocusOut event, serial 35, synthetic NO, window 0x1e00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 35, synthetic NO, window 0x1e00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 35, synthetic NO, window 0x1e00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 35, 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   0   0   0   0   0   0   0   0   0   0   0

##  \ \     /       |
##   \ \   /  _ \   |  |   |  __ `__ \    _ \    |   |  __ \
##    \ \ /  (   |  |  |   |  |   |   |   __/    |   |  |   |
##     \_/  \___/  _| \__,_| _|  _|  _| \___|   \__,_|  .__/
                                                    _|

FocusOut event, serial 35, synthetic NO, window 0x1e00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 35, synthetic NO, window 0x1e00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 35, synthetic NO, window 0x1e00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 35, 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   0   0   0   0   0   0   0   0   0   0   0

##   \  |         |         
##  |\/ |  |   |  __|   _ \ 
##  |   |  |   |  |     __/ 
## _|  _| \__,_| \__| \___| 

FocusOut event, serial 35, synthetic NO, window 0x1e00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 35, synthetic NO, window 0x1e00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 35, synthetic NO, window 0x1e00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 35, 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   0   0   0   0   0   0   0   0   0   0   0

Offline

#2 2019-02-18 14:00:39

Maniaxx
Member
Registered: 2014-05-14
Posts: 738

Re: Volume keys not being recognized

josemota wrote:

When I attempt to use any of three volume keys (up keycode 115 / down keycode 114 / mute keycode 113), they are not recognized.

Recognized by what exactly? There has to be an application assigned to it. I'm using 'volumeicon' (under xfce) for that.

Last edited by Maniaxx (2019-02-18 14:45:21)

sys2064

Offline

#3 2019-02-18 14:17:42

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,571
Website

Re: Volume keys not being recognized

Your xev output is what you would see when some process has bound the keys.  Have you attempted to bind those keys in your i3 config, or via xbindkeys, or anywhere else?

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#4 2019-02-19 16:29:22

josemota
Member
Registered: 2010-10-24
Posts: 47

Re: Volume keys not being recognized

Just a note that I have read your observations and I'll try again soon and report back. Thanks.

Offline

#5 2019-02-20 12:12:34

josemota
Member
Registered: 2010-10-24
Posts: 47

Re: Volume keys not being recognized

I haven't had the opportunity to test this out on my desktop. However, running xev in my Fedora laptop gave me the following output, which clearly identifies XF86AudioRaiseVolume/LowerVolume/Mute:

KeymapNotify event, serial 36, synthetic NO, window 0x0,
    keys:  4294967273 0   0   0   0   0   0   0   0   0   0   0   0   0   0   4   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 36, synthetic NO, window 0x6a00001,
    root 0x182, subw 0x0, time 10790938, (243,-188), root:(243,677),
    state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

FocusOut event, serial 39, synthetic NO, window 0x6a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 39, synthetic NO, window 0x6a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 39, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   8   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 39, synthetic NO, window 0x6a00001,
    root 0x182, subw 0x0, time 10792663, (243,-188), root:(243,677),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

FocusOut event, serial 39, synthetic NO, window 0x6a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 39, synthetic NO, window 0x6a00001,
    mode NotifyUngrab, detail NotifyAncestor

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

KeyRelease event, serial 39, synthetic NO, window 0x6a00001,
    root 0x182, subw 0x0, time 10794316, (243,-188), root:(243,677),
    state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Offline

#6 2019-02-20 12:46:48

Maniaxx
Member
Registered: 2014-05-14
Posts: 738

Re: Volume keys not being recognized

That doesn't matter. I have the same behavior on my system and it works properly. Other tools like showkeys or xinput might show the results you might expect though.

As far as i can tell everything looks fine regarding key capture. It's the target app that seems to be missing on your end.

sys2064

Offline

Pages: 1

Board footer

Powered by FluxBB