mirror of
https://git.sr.ht/~eliasnaur/gio
synced 2026-07-01 07:35:40 +00:00
55c96adb91
Not all wayland compositors advertise the global registry events in the same order. In particular, river and sway differ in that sway advertises the data_device_manager before the seat, and river does it after. This commit updates our code to correctly bind the data_device so that we can work with the clipboard regardless of the registry event order. Special thanks to Isaac Freund (river maintainer) for helping me find the root of this problem. You can see Isaac's extremely helpful and detailed analysis here: https://github.com/riverwm/river/issues/554#issuecomment-1059750874 Signed-off-by: Chris Waldon <christopher.waldon.dev@gmail.com>