search

quackduck / uniclip

Cross-platform shared clipboard
MIT License
246 stars 27 forks source link

Bug: uniclip does not gracefully handle alternative forms (eg. an image) of clipboard content #23

Open awik32 opened 6 months ago

awik32 commented 6 months ago

Description of the bug When a picture (and probably other forms of non-text data) gets added to the clipboard, uniclip hangs with the following output:

verbose: [sent: An error occurred wile getting the local clipboard]
error: [exit status 1]
error: [exit status 1]
error: [exit status 1]
...
error: [exit status 1]
^C

Verbose output (Use the --debug option) See above.

Steps to Reproduce For example, you might send a screenshot to the clipboard.

Expected behavior Either print an error message and resume normal operations, or send the non-text data to the clients. Perhaps this should be configurable.

Cheers, Albert.

quackduck commented 6 months ago

What OS is this on? If linux, what clipboard utility are you using?

awik32 commented 6 months ago

Yes, the server is Linux (Mint 21.2). If I recall correctly, the clipboard utility is "xclip".

quackduck commented 4 months ago

Does the error: [exit status 1] print in an infinite loop? And does this not happen with just regular text?

awik32 commented 4 months ago

Once the error starts printing, it appear to loop endlessly, about once every second, until the the offending content (the image) is removed from the clipboard. There is no error with regular text.