So, obviously this is somewhat user error, since clipmenu doesn't support wayland, because it depends on xsel e.t.c..
I'm aware of that but I just tried out a new desktop environment without double checking whether my systemd would start anything Xserver related, and my cpu got pegged pretty high as clipmenud was spinning trying to access the Xserver.
Can we do a check for this and fail outright, or after a few attempts if that is the case?
example output:
$ systemctl --user status clipmenud
clipmenud.service - Clipmenu daemon
Loaded: loaded (/usr/lib/systemd/user/clipmenud.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-06-08 21:52:50 BST; 3min 55s ago
Main PID: 31347 (bash)
CGroup: /user.slice/user-1000.slice/user@1000.service/clipmenud.service
└─31347 bash /usr/bin/clipmenud
Jun 08 21:56:46 archlinux clipmenud[264750]: : Connection refused
Jun 08 21:56:46 archlinux clipmenud[264759]: xsel: Can't open display: (null)
Jun 08 21:56:46 archlinux clipmenud[264759]: : Connection refused
Jun 08 21:56:46 archlinux clipmenud[264782]: Can't open X display
Jun 08 21:56:46 archlinux clipmenud[264789]: xsel: Can't open display: (null)
Jun 08 21:56:46 archlinux clipmenud[264789]: : Connection refused
So, obviously this is somewhat user error, since clipmenu doesn't support wayland, because it depends on
xsele.t.c..I'm aware of that but I just tried out a new desktop environment without double checking whether my systemd would start anything Xserver related, and my cpu got pegged pretty high as clipmenud was spinning trying to access the Xserver.
Can we do a check for this and fail outright, or after a few attempts if that is the case?
example output: