#830 Mumble ignores mouse binds until a key is pressed

1.2.3
open
nobody
Mumble (544)
5
2012-10-30
2011-09-28
Aaron Faanes
No

On start, Mumble ignores or doesn't respond to mouse bindings (for push-to-talk in my case). If a key is pressed while the Mumble window is focused, all bindings work as intended.

System

Mumble 1.2.3 on Fedora 15, 64-bit

$ rpm -q mumble
mumble-1.2.3-3.fc15.x86_64
$ uname -a
Linux fritocomp 2.6.40.4-5.fc15.x86_64 #1 SMP Tue Aug 30 14:38:32 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
$ pulseaudio --version
pulseaudio 0.9.22
$ ls -l /dev/input/event*
crw-r-----. 1 root root 13, 64 Sep 27 22:28 /dev/input/event0
crw-r-----. 1 root root 13, 65 Sep 27 22:28 /dev/input/event1
crw-r-----. 1 root root 13, 66 Sep 27 22:28 /dev/input/event2
crw-r-----. 1 root root 13, 67 Sep 27 22:28 /dev/input/event3
crw-r-----. 1 root root 13, 68 Sep 27 22:28 /dev/input/event4
crw-r-----. 1 root root 13, 69 Sep 27 22:28 /dev/input/event5

How to Reproduce

  1. Open Mumble
  2. Attempt to use mouse bindings. No bind occurs.

Workarounds

You can press a button right when Mumble starts to work-around this issue. Any keypress while Mumble is focused will fix the issue; it doesn't have to be bound within Mumble.

Discussion

It appears that Mumble doesn't begin listening to input events until a key is pressed. A key being pressed bootstraps the listening process. While this would normally be sufficient, for those with purely mouse-based binds are not likely to press a keybind on start.

This issue is fixed in git HEAD.

Discussion