Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not starting on Pop_OS! 24.04 #44

Open
dolence opened this issue Feb 11, 2025 · 1 comment
Open

Not starting on Pop_OS! 24.04 #44

dolence opened this issue Feb 11, 2025 · 1 comment

Comments

@dolence
Copy link

dolence commented Feb 11, 2025

Installed package `clipboard-history-wayland v0.9.2` (executable `ringboard-wayland`)
Created symlink /home/dolence/.config/systemd/user/graphical-session.target.wants/ringboard-wayland.service → /home/dolence/.config/systemd/user/ringboard-wayland.service.
Failed to start ringboard-wayland.service: Unit ringboard-wayland.service has a bad unit file setting.
See user logs and 'systemctl --user status ringboard-wayland.service' for details.
Failed to restart ringboard-server.service: Unit ringboard-server.service has a bad unit file setting.
See user logs and 'systemctl --user status ringboard-server.service' for details.

❯ systemctl --user status ringboard-server.service
× ringboard-server.service - Ringboard server
    Loaded: bad-setting (Reason: Unit ringboard-server.service has a bad unit file setting.)
    Active: failed (Result: exit-code) since Tue 2025-02-11 17:28:47 -03; 5min ago
      Docs: https://github.com/SUPERCILEX/clipboard-history
  Main PID: 4276 (code=exited, status=203/EXEC)
       CPU: 590us

fev 11 17:28:47 pop-os systemd[2113]: ringboard-server.service: Failed with result 'exit-code'.
fev 11 17:28:47 pop-os systemd[2113]: Failed to start ringboard-server.service - Ringboard server.
fev 11 17:29:16 pop-os systemd[2113]: ringboard-server.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
fev 11 17:29:16 pop-os systemd[2113]: ringboard-server.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
fev 11 17:29:17 pop-os systemd[2113]: ringboard-server.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
fev 11 17:29:39 pop-os systemd[2113]: ringboard-server.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
fev 11 17:29:39 pop-os systemd[2113]: ringboard-server.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
fev 11 17:29:39 pop-os systemd[2113]: ringboard-server.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
fev 11 17:31:00 pop-os systemd[2113]: ringboard-server.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
fev 11 17:31:01 pop-os systemd[2113]: ringboard-server.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
@SUPERCILEX
Copy link
Owner

Can you run the following commands and share their output?

systemd --version
cat ~/.config/systemd/user/ringboard-wayland.service
cat ~/.config/systemd/user/ringboard-server.service

My guess is that you don't have your path set up correctly (can you run ringboard-server directly?) and so the service files are messed up because of this sed replacement:

sed -i "s|ExecStart=ringboard-server|ExecStart=$(which ringboard-server)|g" ~/.config/systemd/user/ringboard-server.service

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants