Description of the bug
Uniclip prints errors and does not add anything to the clipboard when running in Wayland with xclip (or presumably xsel) installed. I believe this is happening because uniclip uses the first binary it finds here and xclip is prioritized over wl-paste:
https://github.com/quackduck/uniclip/blob/master/uniclip.go#L340
I don't think I actually need xclip so I was able to work around the issue by just uninstalling it. But it might be nice if uniclip was able to handle this somehow or at least provide a more informative warning to explain what's going on.
Verbose output (Use the --debug option)
Run `uniclip 192.168.99.143:42165` to join this clipboard
Connected to device at 192.168.99.155:57625
error: [exit status 1]
verbose: [sent: An error occurred wile getting the local clipboard]
error: [exit status 1]
error: [exit status 1]
error: [exit status 1]
Steps to Reproduce
- Install uniclip on two machines, with one machine running Sway (I expect other Wayland environments are also affected but haven't tested it) and having xclip installed
- Start uniclip as usual by running
uniclip on the Wayland machine than uniclip <ip address> on the other
- You will start seeing error messages similar to the ones above on the Wayland machine as soon as the two are connected
Expected behavior
Uniclip should run without errors in Wayland and share the clipboard between machines as normal. Or perhaps print a warning that there are multiple possible clipboard sources so it's clearer what was going on.
OS and Uniclip version
On the Wayland machine I was running the dev version of uniclip cloned from this GitHub on ArchLinux.
The other machine was Windows 10 running uniclip 2.3.6.
Description of the bug
Uniclip prints errors and does not add anything to the clipboard when running in Wayland with xclip (or presumably xsel) installed. I believe this is happening because uniclip uses the first binary it finds here and xclip is prioritized over wl-paste:
https://github.com/quackduck/uniclip/blob/master/uniclip.go#L340
I don't think I actually need xclip so I was able to work around the issue by just uninstalling it. But it might be nice if uniclip was able to handle this somehow or at least provide a more informative warning to explain what's going on.
Verbose output (Use the
--debugoption)Steps to Reproduce
uniclipon the Wayland machine thanuniclip <ip address>on the otherExpected behavior
Uniclip should run without errors in Wayland and share the clipboard between machines as normal. Or perhaps print a warning that there are multiple possible clipboard sources so it's clearer what was going on.
OS and Uniclip version
On the Wayland machine I was running the dev version of uniclip cloned from this GitHub on ArchLinux.
The other machine was Windows 10 running uniclip 2.3.6.