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

part.1: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2068
part.2: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2099
part.3: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2100

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2393
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2393

** Changed in: oem-priority
     Assignee: jeremyszu (os369510) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1966635

Title:
  can't move file/directory by drag and drop by using touch monitor

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Can't move file/directory by drag and drop by using a touch monitor

  OS: 22.04, up to date @ Mar 28, 2022.
  nautilus: 1:42~rc-1-ubuntu1
  mode: wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to