Pulse audio not working with keys? (Solved)

Technical Issues
1

My key presses are recognized as XF86 events, but don’t actually do anything. The only one that works is one i changed to make F5(?) launch flameshot. Here is the results of xev for my most often used keys


KeyRelease event, serial 48, synthetic NO, window 0x2a00001, root 0x5f3, sub OxO, time 126346, (523, -95), root: (634,226),
state Oxo, keycode 123 (keysym 0x1008f13, XF86AudioRaiseVolume), same_screen YES,
KeysymToKeycode returns keycode: 76
LookupString gives 0 bytes:
FilterEvent returns: False

KeyPress event, serial 48, synthetic NO, window 0x2a00001,
root 0x5f3, subw 0x0, time 128650, (523, -95), root: (634,226),
state Oxo, Keycode 122 (keysym 0x1008f11, X86AudioLowerVolume), same_screen YES,
KeysymToKeycode returns keycode: 75
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
FilterEvent returns: False

KeyRelease event, serial 48, synthetic NO, window 0x2a00001,
root 0x5f3, subw ex®, time 123739, (523, -95), root: (634,226),
state ex®, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES, keysymToKeycode returns keycode: 75
XLookupString gives 0 bytes:
FilterEvent returns: False

KeyPress event, serial 48, synthetic NO, window 0x2a00001,
root 8x5f3, subw 8x0, time 129994, (523,-95), root: (634,226), state ex®, keycode 121 (keysym 0x1008f12, XF86AudioMute), same_screen YES,
KeysymToKeycode returns keycode: 74
LookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
FilterEvent returns: False

KeyRelease event, serial 48, synthetic NO, window 0x2a00001,
- root 0x5f3, subw Ox®, time 130117, (523, -95), root: (634,226), state ex®, keycode 121 (keysyn 0x1008ff12, XF86Audiolute), same_screen YES,
KeysynToKeycode returns keycode: 74
LookupString gives 0 bytes:
FilterEvent returns: False
2

XF86AudioRaiseVolume, XF86AudioLowerVolume and XF86AudioMute are preconfigured by default, and they should just work.

Check your ~/config/openbox/rc.xml file around line 600.

3

I was in and out of rc.xml trying to get my volume to work. I eventually got it working. I think all i did was change my keyboard from chromebook to default & back to chromebook again and it worked. :man_shrugging:

4

Also thank you for reminding me i had this up!