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

Change to RemainAfterExit=yes in alsa-restore.service.in #171

Closed
wants to merge 1 commit into from
Closed

Change to RemainAfterExit=yes in alsa-restore.service.in #171

wants to merge 1 commit into from

Conversation

stele95
Copy link

@stele95 stele95 commented Oct 4, 2022

Fresh Manjaro installation.
Default volume value was 75%, no matter to what value I change it, it resets to 75% on reboot/shutdown.

After changing to RemainAfterExit=yes from RemainAfterExit=true in alsa-restore.service, the volume value is properly saved and restored on reboot/shutdown. I did check the following link and it says:

RemainAfterExit=
Takes a boolean value that specifies whether the service shall be considered active even when all its processes exited. Defaults to no.

But if you look at Example 4. Stoppable oneshot service, it clearly sets RemainAfterExit=yes with Type=oneshot.

Fresh Manjaro installation.
Default volume value was 75%, no matter to what value I change it, it resets to 75% on reboot/shutdown.

After changing to `RemainAfterExit=yes` from `RemainAfterExit=true` in `alsa-restore.service`, the volume value is properly saved and restored on reboot/shutdown. I did check the following [link](https://www.freedesktop.org/software/systemd/man/systemd.service.html) and it says:

> RemainAfterExit=
> Takes a boolean value that specifies whether the service shall be considered active even when all its processes exited. Defaults to no.

But if you look at `Example 4. Stoppable oneshot service`, it clearly sets `RemainAfterExit=yes` with `Type=oneshot`.
@stele95
Copy link
Author

stele95 commented Oct 5, 2022

It's worth pointing out that I tried again with true and 1 values and worked both times. Not sure why it wasn't working with true in the first place.

@stele95
Copy link
Author

stele95 commented Oct 5, 2022

Will close the PR since it seems the problem is elsewhere

@stele95 stele95 closed this Oct 5, 2022
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

Successfully merging this pull request may close these issues.

None yet

1 participant