ClipCascade try to use wayland on xserver

[Unknow0]

Hi,

i run clipcascade (3.0.0) from .config/openbox/autostart.sh (i added --xmode then --gui to try to force the x11 usage instead of wayland)

[ "$DISPLAY" = ":0" ] && (sleep 1
        python3 /opt/ClipCascade/main.py --xmode true --gui true > ~/.clipcascade.log 2>&1 &
)

but in the log i seem clipcascade try to use wayland:

(main.py:1956): libayatana-appindicator-WARNING **: 09:32:50.781: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.

(main.py:1956): Gdk-CRITICAL **: 09:32:50.930: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Failed to connect to a Wayland server: No such file or directory
Note: WAYLAND_DISPLAY is unset (falling back to wayland-0)
Note: XDG_RUNTIME_DIR is set to /run/user/1001
Please check whether /run/user/1001/wayland-0 socket exists and is accessible.
Failed to connect to a Wayland server: No such file or directory
Note: WAYLAND_DISPLAY is unset (falling back to wayland-0)
Note: XDG_RUNTIME_DIR is set to /run/user/1001
Please check whether /run/user/1001/wayland-0 socket exists and is accessible.

if i launch it manually sometime it works as expected, but sometime i have the same issue as the autostart.sh

do you know why it try wayland instead of x11 even with --xmode true ?

the env variable i have:

$ echo $XDG_SESSION_TYPE
x11
$ echo $WAYLAND_DISPLAY

$ echo $DISPLAY
:0

Regards.

[Sathvik-Rao]

Hi @Unknow0 ,

Are you using the latest desktop app version 3.2.0?

You're currently mentioning 3.0.0, and there have been updates since then.

Also, since you are launching it from an Openbox startup script, it is possible the X11 display server or session environment is not fully initialized yet during login/startup. That can sometimes cause different behavior between autostart execution and manually launching the app after the desktop session has fully loaded.

[Unknow0]

Hi @Sathvik-Rao,

I found that xclip -selection clipboard -t TARGETS -o return an error instead of the list of available targets without the -selection clipboard it does return the list as expected

so removing the "-selection, "clipboard", in ClipCascade_Desktop/src/clipboard/clipboard_monitor_linux.py line 79 and 375 does seem to fix my issue

i will try to update to 3.2.0 first if it doesn't fix it i can do a pull request

Regards.

[Unknow0]

Hi @Sathvik-Rao,

i have updated the client to 3.2 and i have the same issue with the xclip command

running clipcascade from openbox/autostart.sh it works half way (copy from it to other pc works, but from other to it doesn't) even with --xmode true --gui true

2026-06-04 12:08:41,544 - INFO - XMODE: True
2026-06-04 12:08:41,545 - INFO - Starting GTK clipboard monitoring for X11 display server.
2026-06-04 12:08:41,648 - INFO - Websocket connected
[...]
2026-06-04 12:09:07,259 - ERROR - Failed to execute command: Command '('wl-copy',)' returned non-zero exit status 1.
2026-06-04 12:09:07,259 - ERROR - Failed to copy data to clipboard: Command '('wl-copy',)' returned non-zero exit status 1.
2026-06-04 12:09:07,259 - ERROR - Failed to convert base64 data to clipboard: Command '('wl-copy',)' returned non-zero exit status 1.

but running from a terminal works, at a glace the env variable seem similar, not WAYLAND, DISPLAY=:0 and all XDG_* env are the same

Do you know what can be the cause ?

Regards.