Program mistakenly thinks Debian XFCE uses Wayland when receiving

[mvidelatraduc]

This is the log for the software installed on Debian XFCE after copying text from an Android device:

2025-03-20 17:00:36,032 - ERROR - Failed to execute command: Command '('wl-copy',)' returned non-zero exit status 1.
2025-03-20 17:00:36,032 - ERROR - Failed to copy data to clipboard: Command '('wl-copy',)' returned non-zero exit status 1.
2025-03-20 17:00:36,032 - ERROR - Failed to convert base64 data to clipboard: Command '('wl-copy',)' returned non-zero exit status 1.

The output of some useful commands:

***@***:~$ echo $XDG_SESSION_TYPE
x11
***@***:~$ echo $XDG_SESSION_DESKTOP
xfce
***@***:~$ echo $WAYLAND_DISPLAY

***@***:~$ echo $DISPLAY
:0.0

The program successfully copies into the server from Debian, but is unable to receive data.

Feel free to let me know if there are any other logs or information necessary.

[mvidelatraduc]

Another output:

***@***:~$ xclip -selection clipboard -t TARGETS -o
TIMESTAMP
TARGETS
MULTIPLE
SAVE_TARGETS
text/html
text/_moz_htmlcontext
text/_moz_htmlinfo
UTF8_STRING
COMPOUND_TEXT
TEXT
STRING
text/plain;charset=utf-8
text/plain
text/x-moz-url-priv

[mvidelatraduc]

I've been able to determine this happens when running nohup python3 (path)/main.py &> /dev/null & at login, but not when the same is executed manually. This is not solved by encapsulating the startup command as provided with sh -c 'cd (path) && nohup python3 main.py &> /dev/null &'. Adding sleep beforehand to ensure everything in the XFCE desktop has loaded beforing loading ClipCascade did not help (this was a bit of wishful thinking on my part). The file ~/.xsession-errors also confirms the variable for X11 is correctly set at login:

Xsession: X session started for *** at jue 20 mar 2025 21:37:08 -03
[.......]
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11

[Sathvik-Rao]

Hey @mvidelatraduc,

Thanks for providing the detailed log. I'll take a look at it, but it might take some time.

[mvidelatraduc]

Hey @mvidelatraduc,

Thanks for providing the detailed log. I'll take a look at it, but it might take some time.

Thanks for attending to this, unfortunately I'm no longer using ClipCascade because it didn't fit my use case, so I won't be able to provide additional input.