Clipse does not auto-start in hyprland

[frodew]

I don't know how to fix this as I think it should work. I am on Fedora 40 with Hyprland, happily using clipse - thanks for the great program!

However, it only works for me after I manually type clipse -listen into the console after startup. The following hyprland setup does not seem to start clipse; and I have no idea why...

source=~/.config/hypr/latte.conf
exec-once = [...]

# use clipse as the clipboard manager
exec-once = clipse -listen

[...]

# clipse
windowrulev2 = float, class:(clipse)
windowrulev2 = size 1200 800, class:(clipse)

[...]

bind = $mainMod, C, exec, kitty --class clipse -e clipse

[...]

Everything else in my config starts just fine. Does anyone have a clue what the issue could be?

[alexandre-dos-reis]

I'm experiencing the same behavior on nixos.

[deksan]

Check if you have wl-clipboard installed it relies on wl-paste at starts that was the issue I had.

[frodew]

Check if you have wl-clipboard installed it relies on wl-paste at starts that was the issue I had.

Unfortunately not for me; thanks - Package "wl-clipboard-2.2.1-3.fc41.x86_64" is already installed.

[deksan]

I used strace -p to find out wl-clipboard was missing :)

[miguelsaliba]

I'm having the same issue on fedora 42 with hyprland. It also correctly works for me when I run it manually. Not sure how to debug this

[M3L6H]

I have clipse correctly starting on Hyprland using the following systemd user service:

[Install]
WantedBy=graphical-session.target

[Service]
ExecStart=clipse -listen
RemainAfterExit=true
Type=oneshot

[Unit]
After=graphical-session.target
Description=Clipse listener
PartOf=graphical-session.target

Hyprland config:

bind=$mainMod SHIFT, C, exec, ghostty --class=com.example.clipse -e 'clipse'
windowrule=float, class:(com.example.clipse)
windowrule=size 622 652, class:(com.example.clipse)

[savedra1]

Hi @frodew

Apologies for the delay in getting back - have you managed to solve this yet? The solution in @M3L6H's comment looks
promising.

If it's still an issue, there should be something helpful in the $XDG_CONFIG_HOME/clipse/clipse.log file.

Thanks