GTK applications segfault on wayland with tablet tool input
Steps to reproduce
- Open GTK3 application (I've successfully managed to reproduce this with evince, remmina, nautilus and xournalpp, I'm pretty sure almost every gtk3 app will do this).
- Use your "tablet tool" to hover over something, if you hit/use a button to simulate a right-click it usually happens faster.
- Repeat 2. a few times, watch the program segfault.
Current behavior
Using GTK applications with a "tablet tool" causes the following segfault.
"xournalpp" received signal SIGSEGV, Segmentation fault.
#0 0x00007ffff626fda2 in wl_proxy_marshal (proxy=0x55555590d400, opcode=opcode@entry=0) at src/wayland-client.c:782
#1 0x00007ffff75c04c1 in zwp_tablet_tool_v2_set_cursor (hotspot_y=<optimized out>, hotspot_x=<optimized out>, surface=<optimized out>, serial=<optimized out>, zwp_tablet_tool_v2=<optimized out>) at ./gdk/wayland/tablet-unstable-v2-client-protocol.h:1205
(see attached backtraces for more)
Expected outcome
Dont segfault when using "tablet tool".
Version information
- GTK3 3.24.13 (from eschwartz repository with debug symbols, but extra/gtk3 does the same)
- ArchLinux
- swaywm/wlroots
- MS Surface Go with Pen/tablet tool/stylus
Additional information
Complete backtraces with debugging symbols:
- xournalpp xournalpp_crash1.gdblog
- evince evince_crash1.gdblog
- remmina remmina_crash1.gdblog
Videos:
Edited by Alexander Kempen