Alright I managed to fix this. For some reason all the files in /dev/input weren't part of plugdev and didn't have the correct permissions. Fixing this corrected the issue!
On Fri, Sep 5, 2014 at 4:36 PM, blackops7799 . <blackops7...@gmail.com> wrote: > Whoops, sorry about not CCing the bug report. This is my first time doing > this. > > Anyway, I checked and I am in most certainly in the plugdev group. > > jake@debian:~$ groups jake > jake : jake cdrom floppy sudo audio dip video plugdev scanner bluetooth > netdev > > > On Fri, Sep 5, 2014 at 4:29 PM, Chris Knadle <chris.kna...@coredump.us> > wrote: > >> On Friday, September 05, 2014 16:02:13 blackops7799 . wrote: >> > AHA! I think I figured this out. Okay so, my keyboard has media keys >> and it >> > turns out it's detecting those keys as a separate keyboard and I am >> able to >> > set them as a shortcut. Now for some reason, while under a normal user, >> > mumble will only detect the media keys as the only input device as seen >> in >> > the console. >> > >> > GlobalShortcutX: /dev/input/event16: Microsoft Wired Keyboard 600 >> > >> > However, when ran as root it detects all of my input devices just fine. >> > >> > GlobalShortcutX: /dev/input/event0: Power Button >> > GlobalShortcutX: /dev/input/event1: Power Button >> > GlobalShortcutX: /dev/input/event15: Microsoft Wired Keyboard 600 >> > GlobalShortcutX: /dev/input/event16: Microsoft Wired Keyboard 600 >> > GlobalShortcutX: /dev/input/event17: Logitech Unifying Device. Wireless >> > PID:101a >> > >> > Maybe I have some permissions issues? I'm not really sure. >> >> That might be. See if your username is listed as part of the 'plugdev' >> group >> in /etc/group. If not, run 'adduser <username> plugdev' as root, then >> log out >> of your X session and back in and see if that fixes it. >> >> -- Chris >> >> -- >> >> Chris Knadle >> chris.kna...@coredump.us >> > >
