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

[awik32]

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]

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

[awik32]

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

[quackduck]

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

[awik32]

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.