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

systemPackages not available after reboot #170

Open
Noriller opened this issue Dec 9, 2024 · 0 comments
Open

systemPackages not available after reboot #170

Noriller opened this issue Dec 9, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Noriller
Copy link

Noriller commented Dec 9, 2024

I'm using it in Fedora Silverblue.
Fixed SELinux issues with fix in #51

Services are installed and systemPackages are available.

1- should those be available only for root? (I can run using the path, and add the path later to the user, but just want to confirm) (EDIT: forgot zsh quirks)

The main problem is that the /run folder is cleaned on boot (and the systemPackages are left in /run/system-manager/sw/bin/) and the service that creates it (system-manager-path.service) is of type oneshot, so it's not persisting.

2- So, is it possible to configure it so it will be always run? (and/or changing where it saves that bin folder?)

@Noriller Noriller added the bug Something isn't working label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant