Wayland backend: add host-to-client clipboard sync (revived)

[ninetailedtori]

I'd welcome testing on this, it should implement the clipboard protocol correctly, without crashing randomly on tab out tab ins/copy-pasting invalid mime types into gamescope.

[cwildfoerster]

+1, works as excpected, can copy&paste fine into cs2. i guess .gitignore change should be removed.

XKB_DEFAULT_LAYOUT="de(nodeadkeys)" LD_PRELOAD="" /home/user/Downlods/gamescope/build/src/gamescope -w 1280 -h 960 -W 2560 -H 1440 -S stretch -f --force-grab-cursor --expose-wayland -- %command% -console

[ninetailedtori]

+1, works as excpected, can copy&paste fine into cs2. i guess .gitignore change should be removed.

XKB_DEFAULT_LAYOUT="de(nodeadkeys)" LD_PRELOAD="" /home/user/Downlods/gamescope/build/src/gamescope -w 1280 -h 960 -W 2560 -H 1440 -S stretch -f --force-grab-cursor --expose-wayland -- %command% -console

I'll push the revert to gitignore, good catch. :]

[ninetailedtori]

Any crashes to note? Has anyone tested if image clipboard content outside the app destroys the offer correctly and doesn't post a garbled mess? My own testing seems reasonably stable :)

[hucet]

Hi, thanks for the update! The clipboard sync worked for me.

I found a crash related to drag and drop: When I drag a file (or text) from my host and hover it over the game window, gamescope crashes immediately. The window disappears, but the process seems to remain active in the background.

The logs show a lot of these errors when the crash happens:

[gamescope-clipboard] [Error]  xdg_backend: Compositor released us but we were not acquired. Oh no.
[gamescope-clipboard] [Warn]  xwm: got the same buffer committed twice, ignoring.

My Setup:

• Distro: CachyOS (Arch based) with Gnome
• Game: World of Warcraft Classic and Battlenet via Lutris
• Arguments: -w 7680 -h 2160 -W 7680 -H 2160 -r 240 -f --force-grab-cursor

Is this happening only on my end/setup?

[ninetailedtori]

Replying to #2062 (comment)

This isn't enough log, unfortunately. Are you running with debug option on gamescope? I'd need a log on the bug reproduction to try to diagnose what was happening :]