After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 783720 - Wacom tablet tools (e.g. stylus, puck) unable to resize GTK3 windows under Wayland
Wacom tablet tools (e.g. stylus, puck) unable to resize GTK3 windows under Wa...
Status: RESOLVED DUPLICATE of bug 777333
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-06-12 23:11 UTC by Jason Gerecke
Modified: 2017-07-21 09:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jason Gerecke 2017-06-12 23:11:46 UTC 
Wacom tablet tools like a pen or puck are apparently unable to resize GTK3 windows under Wayland. The cursor changes to the proper icon, but the window does not respond to the drag. Programs which GTK2 (e.g. GIMP) or Qt (e.g. Chromium) don't change their icon at the edge of the window, but *do* allow resizing to occur.

I wonder if this is in any way related to #777333. In both cases it seems like only GTK3 applications are affected, with "drag" events on the frame/titlebar apparently not being processed.
Comment 1 Jason Gerecke 2017-06-15 21:30:51 UTC 
Mucking around in GDB, it does indeed appear that this is related to bug 777333. The difference is that GTK has `gdk_wayland_window_begin_resize_drag` call `zxdg_toplevel_v6_resize`, which is handled by Mutter as `xdg_toplevel_move`, which calls `meta_wayland_seat_get_grab_info` -- which fails for the same reason as in the window move case.
Comment 2 Jason Gerecke 2017-06-15 21:31:45 UTC 
Correction: that should say `xdg_toplevel_resize`, not `xdg_toplevel_move`.
Comment 3 Carlos Garnacho 2017-07-21 09:30:42 UTC 
This is indeed the same than bug #777333, since moving and resizing are both tied to the same protocol and compositor operation.

*** This bug has been marked as a duplicate of bug 777333 ***