After some checks, it seems because data_device_start_drag() doesn't support MetaWaylandTouch.
The fix will impact the mutter architecture and it's more likely a feature request in mutter so far.
It can be workaround by either sync MetaWaylandPointer motion and MetaWaylandTouch when meta_wayland_seat_update() or meta_wayland_seat_handle_event() with some tweaks. or some changes in meta_wayland_data_device_start_drag().
As maintainer mentions[1] the drag feature is refactoring
After some checks, it seems because data_device_ start_drag( ) doesn't support MetaWaylandTouch.
The fix will impact the mutter architecture and it's more likely a feature request in mutter so far. seat_update( ) or meta_wayland_ seat_handle_ event() with some tweaks. or some changes in meta_wayland_ data_device_ start_drag( ).
It can be workaround by either sync MetaWaylandPointer motion and MetaWaylandTouch when meta_wayland_
As maintainer mentions[1] the drag feature is refactoring
part.1: https:/ /gitlab. gnome.org/ GNOME/mutter/ -/merge_ requests/ 2068 /gitlab. gnome.org/ GNOME/mutter/ -/merge_ requests/ 2099 /gitlab. gnome.org/ GNOME/mutter/ -/merge_ requests/ 2100
part.2: https:/
part.3: https:/
and this issue might be fixed in part.5...
For both workaround look not suitable with the maintainer's design.
I prefer to wait until the refactoring completed by maintainer.
[1] https:/ /gitlab. gnome.org/ GNOME/mutter/ -/issues/ 2393#note_ 1532698