| Summary: | gtk_clipboard_set_with_owner() does not work on kwin wayland | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Giovanni <giodev> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | normal | CC: | kde |
| Priority: | NOR | ||
| Version First Reported In: | 5.26.4 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | GTK+ 3 example program to reproduce the bug. | ||
|
Description
Giovanni
2022-12-25 18:02:25 UTC
"UTF8_STRING" is not a valid mimetype. I can see kwin copy that, but no client will think it has readable clipboard contents. If I change your example to "text/plain" or "text/plain;charset=utf-8" it works as expected. The way mimetype's name themselves is a bit random. We do have a translation of text mime names for x11 applications in kwin, as well as some translations inside the Qt wayland backend to make apps use the right standard. Presumably mutter has a translation layer for wayland apps too, which helps hide this? But ultimately this is still a client bug and should be fixed at the root. Can you confirm that this resolves the real problem in Remina? FYI: if you open krunner (alt+space) and type "kwin" you can get a kwin debug console. There is a tab called "Clipboard in there" which can view contents. Thank you, changing UTF8_STRING to text/plain;charset=utf-8 worked. You saved me ! ;) But I need to do more regression testing to ensure text/plain;charset=utf8 works also on older (max 4-6 years) Xorg. If it does not work, the application (Remmina) should expose two different formats to the clipboard, I think. |