10:58 kaiser2nd: Good morning, is there somewhere I am able to track the clipboard issue thats affecting wayland compositors?
10:58 vyivel: "the" clipboard issue?
10:59 kaiser2nd: The particular issue where copy and paste does not work, or is very unreliable at best
11:00 kaiser2nd: I have spoken to some people over on discord who are having the identical issue but on different compositors, using different clipboard managers, but cannot find anywhere to track this, for example a git issue
11:00 kennylevinsen: You'll have to be a bit more specific - I don't know any any clipboard issues, and it's reliable.
11:00 vyivel: ^
11:00 kaiser2nd: thats interesting to hear
11:01 kennylevinsen: clipboard *managers* being unreliable would be another thing, sounds more like a bug in those
11:01 kennylevinsen: (I always recommend starting discussion at the client or server having a specific issue, and only escalating when devs suspect the issue is higher up)
11:04 kaiser2nd: for background context, I am using hyprland and cliphist. clipboard functionality, for I'd have to roughly estimate, the last couple months(?) have been quite broken. For instance, I am able to copy text from firefox into kitty(terminal) but not vice versa, cannot copy text from anywhere else into discord, screenshotting images into my clipboard and pasting it is very unreliable and takes tens of tries
11:04 kaiser2nd: for a succesfull upload. In general, with some exceptions (such as firefox -> terminal) the clipboard seems to only know what has been copied in thar particular application. An example of this would be copying something in discord, for example, attempting to paste it into firefox, what will be pasted is not the contents of what was copied in discord, but rather whatever was previously copied within
11:04 kaiser2nd: firefox itself.
11:05 kennylevinsen: start out by removing cliphist from the equation (make sure it's not running)
11:05 kennylevinsen: then you have three components: firefox, kitty and hyprland. If you cannot copy between those two, then the issue is in one of those three components.
11:06 kaiser2nd: I assumed this was an issue with hyprland, or even perhaps that I am not even using a actual clipboard program, So I install cliphist and ensured it doesnt conflict with any other clipboard program and is started on login. the issue persisted.
11:06 kennylevinsen: You do not need any clipboard manager, those solely exist to add *extra* functionality like persistence once the source app clsoes.
11:06 kaiser2nd: But I brought this up in a linux discord server, and someone was having the same issue on hyprland as well, he believes the issue is on waylands side. and another person came forward who doesnt use hyprland, they use wayfire, and they have the same exact issue as me, and is also using a different clipboard manager (copyq iirc)
11:07 kennylevinsen: If it reproduces without cliphist, then it's a hyprland, kitty or firefox issue.
11:07 kennylevinsen: kaiser2nd: "wayland" is mainly just a protocol specification, so suspicion of issues in Wayland mainly mean suspicion that the protocol specification is unable to provide a specific functionality.
11:08 kaiser2nd: the person reporting it on wayfire also said they were having this issue with sublime as well
11:08 kennylevinsen: For all intents and purposes, that's the *last* step in the debug chain, once one has established that the client and server works as per protocol, and that the protocol has a flaw
11:09 kaiser2nd: I understand the nature of wayland, in my mind, when I see several people having the same issue using different software, where the only common denonimator is wayland, and this being confidently asserted by others as well, i assumed there would be a git issue or something along those lines, thats why im here
11:09 kennylevinsen: kaiser2nd: mixing servers, clients and clipboard managers is not useful. Step one is to debug a single incident and figure out *why* one cannot copy from kitty
11:10 kennylevinsen: Step 1 there would be analyzing the wayland messages (WAYLAND_DEBUG=1 kitty for example), and finding the faulty pattern (kitty not providing a data offer? firefox not accepting?)
11:10 kennylevinsen: I don't see any reason to suspect the protocols at the current time
11:11 kennylevinsen: I fully expect this to be a bug between the interacting parties, although I can of course be proven wrong later :)
11:11 kennylevinsen: but note: in any debugging, make sure *no* clipboard manager is invovled, because that can itself be the cause. Keep it apples to apples, and debug the simplest reproduction with the simplest clients (e.g., maybe avoid firefox for example)
11:15 kennylevinsen: (also note that while I am currently rejecting the hypothesis that it's a protocol issue, I am not saying that you cannot get help in the debugging process - it just doesn't belong on the Wayland issue tracker yet)
11:16 kaiser2nd: I was overly confident that this was a well-known issue i suppose
11:16 kaiser2nd: perhaps some common library or package broke for me and all these people, separate from wayland
11:17 kennylevinsen: I imagine clipboard handling in kitty and hyprland would be handrolled by those projects. Firefox would partly rely on Gtk, and wayfire would partly rely on wlroots.
11:18 kennylevinsen: It could be a bug that's getting copy-pasted around, or a weird corner case, who knows - getting a simple reproduction and looking at the Wayland debug logs would be useful.
11:19 kaiser2nd: what i'll do is record a demonstration of the bug, as well as try to generate some logs to share
11:19 kennylevinsen: starting kitty with `WAYLAND_DEBUG=1 kitty 2> kitty.log` should get you the messages. Try to be brief in your interaction with kitty though, and avoid typing anything sensitive - it'll contain *everything*
11:24 kaiser2nd: ah im using alacritty
11:27 kaiser2nd: you weren't kidding about these logs tracking every single thing
11:29 dottedmag: kaiser2nd: Clipboard handling is a complicated dance between three parties, and whenever any step of any party is wrong the result is "clipboard does not work", so what you see might be the result of multiple bugs in various pieces of software.
11:29 kaiser2nd: https://pastebin.com/7idWS9ZJ
11:29 kaiser2nd: thank god i can copy from firefox to alacritty
11:29 kaiser2nd: anyway thats the logs for alacritty, im not sure if there is anything useful there
11:29 kaiser2nd: its a lot of noise, probably not much constructive in it but who am i to say
11:29 kennylevinsen: it's only useful if it contains a reproduction of the issue
11:30 kennylevinsen: i.e., a failed paste operation
11:30 kennylevinsen: to or from the client you collected the log from
11:30 kaiser2nd: uh, let me do that again then
11:32 kaiser2nd: log is too large for pastebin, whats the popular paste site people are using nowadays?
11:43 dottedmag: try paste.debian.net, maybe it will fit
11:50 kaiser2nd: "413 Request Entity Too Large"
11:50 kaiser2nd: aha
11:50 dottedmag: well, any file-sharing
11:52 kaiser2nd: I should probably host my own personal paste site
12:01 bluetail: kaiser2nd why not use 0x0
12:01 bluetail: https://0x0.st/
12:03 kaiser2nd: oh right, that one
12:03 kaiser2nd: thanks
12:03 kaiser2nd: https://0x0.st/XfEL.log
12:03 kaiser2nd: in this log, I tried to copy something from discord into alacritty
12:04 kaiser2nd: it only pasted what I previously copied in alacritty itself
12:04 vyivel: discord still runs through xwayland, right?
12:06 kaiser2nd: vyivel: i was going to say "not for me" but looking at hyprctl clients, it is.. hm
12:06 kaiser2nd: pretty sure i added wayland launch params..
12:06 kaiser2nd: I will take a look at this after work
12:06 kennylevinsen: alacritty is being spammed by data offers for some reason
12:07 kaiser2nd: well i did try pasting into it, maybe 3 times at most
12:07 kaiser2nd: i think twice
12:08 kennylevinsen: it got 8647 offers
12:08 kaiser2nd: odd
12:08 kaiser2nd: i will try the same thing with kitty when i can
12:08 kennylevinsen: When it was focused, it should get 1 offer (the last one), and no more unless the copy changes
12:08 kaiser2nd: logging it, i mean
12:09 kaiser2nd: I already know the same issue affects kitty as well, but would be good to get logs for that too
12:09 kennylevinsen: receiving offers is not alacritty's fault. Make sure there isn't a clipboard manager running
12:09 kaiser2nd: thats my bad, i forgot to kill cliphist
12:10 kennylevinsen: this could very well be cliphists fault
12:10 kennylevinsen: kaiser2nd: look for the "wl_data_device#BLAH.data_offer(new id wl_data_offer#BLAH)" lines. There shouldn't be many.
12:11 kaiser2nd: https://0x0.st/XfEp.log
12:11 kaiser2nd: cliphist is killed for this one
12:12 kennylevinsen: The offers are still coming. One could try to kill source application to see if they at any point stop, and see if copying from *other* applications also cause it
12:13 kaiser2nd: I need to do work, I will take another look at this after the ball and chain is off
12:13 kennylevinsen: kaiser2nd: there's a good chance that this is hyprland, possibly due to a bad interaction with the source client - there's also extra fun things when the source app is Xwayland
12:14 kaiser2nd: well, at this point, im thinking a fresh installation of my distro might be a solution
12:14 kennylevinsen: I don't see why that would do anything
12:14 kaiser2nd: who knows, i cant articulate the issue, hence the clean slate idea
12:15 kennylevinsen: well the log you sent contain a pretty big issue worth debugging
12:15 kaiser2nd: hm, alright, ill take another look later then before contemplating nuking the install
12:17 kennylevinsen: assuming *no* clipboard manager is running, then it's likely a hyprland bug - possibly in the xwayland clipboard logic as mentioned.
12:18 kennylevinsen: (it could also be the source app spamming the clipboard - I don't remember if *copying* is allowed for unfocused surfaces, only that paste isn't)
14:06 wlb: wayland Issue #414 closed \o/ (protocol: clarify how destroying and recreating a wl_subsurface affects its parent-child relationship and position https://gitlab.freedesktop.org/wayland/wayland/-/issues/414)
14:19 wlb: weston/main: Robert Mader * gl-renderer: Fix limited range quantization https://gitlab.freedesktop.org/wayland/weston/commit/9a754434f1c3 libweston/renderer-gl/fragment.glsl
14:19 wlb: weston Merge request !1554 merged \o/ (gl-renderer: Fix limited range quantization https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1554)
14:28 wlb: weston/main: Daniel Stone * 6 commits https://gitlab.freedesktop.org/wayland/weston/compare/9a754434f1c3cd49877911bbd84cf1ecad781152...2d8c1af8b77c3d28f9d1a44f95d2007a264cdbb1
14:28 wlb: weston Merge request !1582 merged \o/ (Improve texture units usage https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1582)
16:51 wlb: wayland-protocols Merge request !325 opened by Nicolas Fella (nicolasfella) tablet-v2: Fix feedback description in mode_switch https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/325
16:53 Arnavion: Depending on how soon you took the log after killing cliphist, if cliphist spammed offers then it could take a while for compositor to drain the socket to EOF even after cliphist was already dead
19:12 wlb: wayland Merge request !413 opened by Demi Marie Obenour (DemiMarie) src: properly use sendmsg(2) https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/413
19:18 wlb: wayland Merge request !414 opened by Demi Marie Obenour (DemiMarie) Miscellaneous cleanups https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/414
19:21 wlb: wayland Merge request !415 opened by Demi Marie Obenour (DemiMarie) Limit buffers to INT_MAX and respect signedness https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/415
19:48 wlb: wayland Merge request !416 opened by Demi Marie Obenour (DemiMarie) Require messages to use as few bytes as possible https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/416