GNOME Bugzilla – Bug 769030
On Thinkpad Yoga 260 (integrated wacom tablet + touchscreen), GIMP is sometimes stuck in a state where right-click doesn't work
Last modified: 2018-05-24 16:37:59 UTC
On Thinkpad Yoga 260 (integrated wacom tablet + touchscreen), GIMP is sometimes stuck in a state where right-click doesn't work. Sometimes this can be remedied by randomly touching on the screen and hoping it gets somehow unstuck, sometimes this can be remedied by reloading the gnome shell (but this is now unavailable under the new Wayland GNOME Session), and sometimes it just doesn't go away. Since this makes GIMP effectively impossible to use when this happens and you can't get rid of it, this is a fairly big problem. I have never seen this on any other laptop or my desktop, so I suspect it is somehow related to GTK+'s/GIMP's handling of the touchscreen and/or the integrated wacom pen tablet thing. No other application is affected either when GIMP is stuck in such a broken state, context menus and everything work perfectly fine in everything else.
I mainly recall seeing this when an external monitor is attached and the internal one is turned off in the gnome control center. I don't know if it's strictly required for reproducing this though
I also just discovered that right now after that bug has triggered, the close button of the GIMP window does absolutely nothing and the menu bar at the top will highlight any entry when clicked (like "File" or "Colors") but not open up the menu either. This issue happens both with Xorg and under a Wayland session by the way.
Does restarting GIMP fix that problem, or only restarting gnome-shell (under and Xorg session)?
Restarting GIMP doesn't fix it, which is why I'm currently stuck with this state. Since I'm currently running under a wayland session, I can't restart GNOME either. I would assume that restarting the laptop might fix it, at least temporarily. However, I manage getting it somehow to work again under Xorg. I just wildly restarted GNOME shell, GIMP and touched the screen and somehow got it unstuck. It took me a while though, and I'm still not sure how to get rid of it reliably, and the issue reappears quite often.
If restarting GIMP doesn't fix it, I see no reason how this could be GIMP's fault.
I'm not in any position to guess what upstream party could be responsible or even more so notably assist such an upstream party in debugging with the unique application that is GIMP in any smart manner (since no other program seems to be affected). However, if you want me to run some command or collect some logs the next time this happens so you can identify the problematic component, I'd be happy to do so
I have also observed this issue, another way GIMP misbehaves in this state is that the marching ants outline of the current brush does not track the cursor. And the triangles of the levels tool are grabbed and dragged when just hovering over them without pressing. I suspect touching the screen to activate touch screen mode, and alt-tabbing to other applications to deactivate it to be part of unscrewing this behavior.
I'm unclear with the given info about whether this is seen on the gnome X11 session too or just on wayland. If it's seen just on wayland I might suspect to some degree of gnome-shell or Xwayland, if it's seen on X11 too I think it points further down to X11/kernel driver issues. All the described behavior seems to me (X)wayland specific though, if Xwayland is left with a stuck grab, it would only affect X clients, while the compositor and wayland clients could keep working (to some extent, even if the touchpoint is stuck at a lower level). But I guess libinput-debug-events is a good starting point anyway. if TOUCH_DOWN and TOUCH_UP events are not paired, that's certainly a sign of trouble.
The original reporter doesn't mention wayland, and I am not using wayland either, and have only experienced this under gnome X11 sessions with the touchscreen + touchpad combo of my yoga300-11ibr. I'll bring my misbehaving yoga to the catalan masia for the week jan 27th->fosdem, we could debug it there if it remains unresolved.
This is an X11 bug showing for me with a touchscreen + touchpad + trackpoint + wacom pen device in a regular classic X11 GNOME 3 session. Wayland is an absolute disaster due to GTK2 not receiving pen events at all so you can't interact with lots of applications at all, so I don't use GIMP with Wayland.
As carlos said in comment 8, please run sudo libinput-debug-events in the background and try to reproduce it. This should show up any unbalanced events that may cause the button to be held down. Note that l-d-e listens to all devices, any passwords you type will show up in the output. If you can't reproduce the bug quickly enough, please restart l-d-e to keep the recording short.
Created attachment 342888 [details] log of input events that result in the bad state
Created attachment 342889 [details] shorter event capture of input events that makes X / GIMP unstuck
(In reply to Øyvind Kolås from comment #12) > Created attachment 342888 [details] > log of input events that result in the bad state button, touch and key events are balanced so this is unlikely an issue in libinput or lower. I noticed a mix of touch and button events towards the end, so my first guess is that there may be something off with the pointer emulation bits in X11 that results in a stuck grab. it could be that gimp is the only one to trigger this because it (iirc) still uses active grabs on input devices directly.
Testing during GUADEC, I am currently able to reproduce this under debian stretch with xorg, thankfully when using wayland this particular stuck right button state does not occur, and the hardware is almost fully usable. There is however race conditions/lock ups that are similar which seem to be resolved by forcing switches between clients/windows by keyboard shortcuts, where wayland seems to receive no pointer events until unblocked.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/936.