Locks on pan mode

[zoqaeski]

Pressing the space bar to switch between Node and Select tools seems to lock the mouse on pan mode if you move the mouse at the same time. Inkscape completely steals the mouse, and no amount of clicking, keypresses or anything will get it to release short of killing it with SIGTERM. Even switching windows with Alt-Tab keeps the mouse locked in pan mode. The Inkscape interface is completely unresponsive, giving no means to release from pan mode, let alone save a document and gracefully exit.

Inkscape version: 0.91
Distribution: Arch Linux x86-64
Desktop environment: GNOME 3.14

Steps to reproduce:
1. Open a new document (even the blank canvas will do).
2. Select the "Select" (?) tool.
3. Press space and move the mouse simultaneously, or press space, move the mouse and click within a short timeframe (i.e. less than two seconds)

Result: Pan mode is activated and locks.

Expected behaviour: The normal function of the space bar, usually switching between Select and Node.

Attached is a screencast of the behaviour that I'm experiencing. There's no sound, but I've moved the mouse around a bit and tried to click on different elements in the interface, including closing the window; I used Alt-Tab to switch windows but the mouse focus is still locked. I've got my terminal bound to a shortcut, so I trigger that and then kill Inkscape.

I've been able to reproduce this every single time, which was how I managed to trigger it so I could record it.

[su_v (suv-lp)]

Do you happen to use a a Logitech K120 or K200 keyboard?

[su_v (suv-lp)]

Possibly same as earlier report bug #1400234 “Space Key blocks drag and drop” (see also other duplicate bug #1416879).

[zoqaeski (zoqaeski)]

Yeah, my keyboard is a K120. I'm also using a Logitech M90/M100 mouse and a Wacom Bamboo CTH-301K tablet.

[su_v (suv-lp)]

Thank you for reporting back (much appreciated!).

On 2015-03-30 18:56 (+0200), zoqaeski wrote:
> Yeah, my keyboard is a K120.

In this case, linking as duplicate to bug #1400234 (it was confirmed by several users independently that the mentioned keyboard models trigger this issue) - feel free to add a comment here (bug #1438042) and to revert the duplicate status in case you disagree and can provide additional data which would indicate that these are unrelated issues which have to be tracked independently.