Skip to main content
Image

r/voidlinux



Advertisement: Prime Big Deal Days is coming October 6-7. Shop big deals on beauty, electronics, and more.
Prime Big Deal Days is coming October 6-7. Shop big deals on beauty, electronics, and more.
media poster


Installed Void Linux on my 2010 MacBook Pro
Installed Void Linux on my 2010 MacBook Pro
Image r/voidlinux - Installed Void Linux on my 2010 MacBook Pro

Is fully functioning wayland (Niri) clipboard an unsolved computer science problem?
Is fully functioning wayland (Niri) clipboard an unsolved computer science problem?

I quite like Wayland's innovations and enjoy my Niri very much; clipboard persistence is a known problem: if you do Ctrl+C, close the source window, Ctrl+V -- it will paste nothing, because the clipboard is bound to the window. That's a known limitation of the protocol, and I expected that I would need to do some tweaking to make it work, but I actually can not do it at all.

The solutions I encountered are:

  1. wl-clip-persist -- very buggy, at least with Niri. It breaks gedit selection (which is the best GUI text editor I know), firefox is able to copy only 50% of the time

  2. Doing a custom solution on top of a complex clipboard manager like CopyQ. That looks like a terrible overkill that would bring a lot of painful debugging

  3. A lot of suggestions like "do something else" -- install a thing that would have its own separate keyboard, keep history and paste through a picker; switch to KDE/gnome; my favorite is "persistent clipboard is against wayland philosophy => you should not want it", which is just disgusting

The problem seems quite simple: make clipboard act normally. There are a lot of people using wayland, everybody uses clipboard, somebody should know a normal solution, right?