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

hyprpolkitagent cannot be started by systemd #20

Closed
calebperkins opened this issue Dec 26, 2024 · 1 comment
Closed

hyprpolkitagent cannot be started by systemd #20

calebperkins opened this issue Dec 26, 2024 · 1 comment

Comments

@calebperkins
Copy link

The wiki instructions indicate you can either:

Add exec-once = systemctl --user start hyprpolkitagent to your Hyprland config and restart hyprland

Or, if using UWSM:

you can autostart the polkit agent with the command systemctl --user enable --now hyprpolkitagent.service.

However, running either of these commands results in:

The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.

Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.

Is the service file indeed missing an entry? Using exec-once = uwsm app -- /usr/bin/hyprpolkitagent instead works for me.

@calebperkins
Copy link
Author

Apologies, I think the AUR package was outdated. This was fixed in #3.

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

1 participant