Yeah, that error shows up when the service is started before the X server is available. Though, I'm not sure how you got the service to run in the first place, since it depends on graphical-session.target
(which isn't used unless something BindsTo=
it).
I tested it in a VM (bspwm + lightdm) and xmousepasteblock.service
wouldn't start on session init (no errors either).
If sddm is somehow starting graphical-session.target
despite not having a concrete session target, then I would consider that a bug. You can find documentation about this special target in the systemd.special(7)
manual.
For instance, this is what it looks like on GNOME:
graphical-session.target
● ├─*omitted for brevity*
● ├─xmousepasteblock.service
● ├─basic.target
● │ ├─*omitted for brevity*
● ├─gnome-session-wayland.target
● └─gnome-session-wayland@gnome.target
● ├─gnome-session-wayland.target
● ├─gnome-session.target
● │ ├─gnome-session-monitor.service
○ │ ├─gnome-session-signal-init.service
● │ ├─gnome-session-initialized.target
○ │ │ ├─gnome-session-signal-init.service
● │ │ ├─org.gnome.Shell@wayland.service
○ │ │ ├─org.gnome.Shell@x11.service
● │ │ ├─gnome-session-manager.target
● │ │ │ ├─gnome-session-manager@gnome.service
● │ │ │ ├─gnome-session-pre.target
● │ │ │ ├─gnome-session-monitor.service
● │ │ │ ├─graphical-session-pre.target
● │ │ │ └─basic.target
● │ │ │ ├─...
You might want to report this to the bspwm dev, but it might just be easier to add xmousepasteblock &
to your rc file as you mentioned.
Pinned Comments
peelz commented on 2023-03-08 21:41 (UTC) (edited on 2023-03-08 21:41 (UTC) by peelz)
The latest upstream version (1.3) doesn't work for many users, which is why this package is currently pinned to the last known working release (1.2).
It also includes a systemd user service so it can be initialized without having to modify session init scripts manually.
I tested the systemd service on both GNOME (43.3) and KDE Plasma (5.27.2), both appear to work fine.