ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
<kaiser2nd>
Good morning, is there somewhere I am able to track the clipboard issue thats affecting wayland compositors?
<vyivel>
"the" clipboard issue?
<kaiser2nd>
The particular issue where copy and paste does not work, or is very unreliable at best
<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
<kennylevinsen>
You'll have to be a bit more specific - I don't know any any clipboard issues, and it's reliable.
<vyivel>
^
<kaiser2nd>
thats interesting to hear
<kennylevinsen>
clipboard *managers* being unreliable would be another thing, sounds more like a bug in those
<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)
<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
<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
<kaiser2nd>
firefox itself.
<kennylevinsen>
start out by removing cliphist from the equation (make sure it's not running)
<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.
<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.
<kennylevinsen>
You do not need any clipboard manager, those solely exist to add *extra* functionality like persistence once the source app clsoes.
<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)
<kennylevinsen>
If it reproduces without cliphist, then it's a hyprland, kitty or firefox issue.
<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.
<kaiser2nd>
the person reporting it on wayfire also said they were having this issue with sublime as well
<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
<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
<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
<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?)
<kennylevinsen>
I don't see any reason to suspect the protocols at the current time
<kennylevinsen>
I fully expect this to be a bug between the interacting parties, although I can of course be proven wrong later :)
<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)
<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)
<kaiser2nd>
I was overly confident that this was a well-known issue i suppose
<kaiser2nd>
perhaps some common library or package broke for me and all these people, separate from wayland
<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.
<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.
<kaiser2nd>
what i'll do is record a demonstration of the bug, as well as try to generate some logs to share
<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*
mclasen has joined #wayland
<kaiser2nd>
ah im using alacritty
<kaiser2nd>
you weren't kidding about these logs tracking every single thing
<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.
<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
<kaiser2nd>
I need to do work, I will take another look at this after the ball and chain is off
<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
<kaiser2nd>
well, at this point, im thinking a fresh installation of my distro might be a solution
<kennylevinsen>
I don't see why that would do anything
<kaiser2nd>
who knows, i cant articulate the issue, hence the clean slate idea
<kennylevinsen>
well the log you sent contain a pretty big issue worth debugging
<kaiser2nd>
hm, alright, ill take another look later then before contemplating nuking the install
mclasen has quit [Remote host closed the connection]
Moprius has joined #wayland
<kennylevinsen>
assuming *no* clipboard manager is running, then it's likely a hyprland bug - possibly in the xwayland clipboard logic as mentioned.
nerdopolis has quit [Ping timeout: 480 seconds]
<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)
nerdopolis has joined #wayland
Moprius has quit [Quit: bye]
kts has quit [Quit: Konversation terminated!]
kingwill101 has quit [Ping timeout: 480 seconds]
naemi4491 has quit []
naemi4491 has joined #wayland
mclasen has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
Brainium has joined #wayland
alice is now known as psykose
psykose has quit [Remote host closed the connection]
psykose has joined #wayland
psykose_ has joined #wayland
psykose is now known as Guest1565
psykose_ is now known as psykose
Guest1565 has quit [Ping timeout: 480 seconds]
feaneron has joined #wayland
leon-anavi has quit [Remote host closed the connection]
<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
kts has quit [Ping timeout: 480 seconds]
riteo has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
chamlis has quit [Remote host closed the connection]
chamlis has joined #wayland
sally has quit [Remote host closed the connection]
FreeFull has quit [Quit: New kernel version]
sally has joined #wayland
FreeFull has joined #wayland
meltq has joined #wayland
Moprius has joined #wayland
meltq has quit [Remote host closed the connection]
meltq has joined #wayland
meltq has quit [Remote host closed the connection]
Brainium has joined #wayland
privacy has joined #wayland
eroc1990 has quit [Quit: Ping timeout (120 seconds)]