fix: use OnStartupSec instead of OnBootSec for user timers#1268
Merged
RoyalOughtness merged 2 commits intosecureblue:livefrom Aug 19, 2025
Merged
fix: use OnStartupSec instead of OnBootSec for user timers#1268RoyalOughtness merged 2 commits intosecureblue:livefrom
RoyalOughtness merged 2 commits intosecureblue:livefrom
Conversation
Per the systemd documentation (systemd.timer(5)), "the user service manager is generally started on first login only, not already during boot." So, timers for user services should use OnStartupSec instead of OnBootSec, as an activation time relative to boot time could elapse before the user service manager starts, making the timer fail to trigger as expected. Also did some minor cleanup on timers and services: * Adjusted the timing for `secureblue-flatpak-setup.timer` to simply use `OnStartupSec=5s`. * Removed `Persistent=true` from timers with no `OnCalendar` trigger, as it has no effect on such timers. * Added `--noninteractive` to the `flatpak install` commands in the flatpak setup script to avoid flooding the system journal with download progress messages while it's running. Signed-off-by: Daniel Hast <[email protected]>
RoyalOughtness
approved these changes
Aug 19, 2025
RKNF404
approved these changes
Aug 19, 2025
Rubiginosa
approved these changes
Aug 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per the systemd documentation (systemd.timer(5)), "the user service manager is generally started on first login only, not already during boot." So, timers for user services should use OnStartupSec instead of OnBootSec, as an activation time relative to boot time could elapse before the user service manager starts, making the timer fail to trigger as expected.
Also did some minor cleanup on timers and services:
secureblue-flatpak-setup.timerto simply useOnStartupSec=5s.Persistent=truefrom timers with noOnCalendartrigger, as it has no effect on such timers.--noninteractiveto theflatpak installcommands in the flatpak setup script to avoid flooding the system journal with download progress messages while it's running.This should fix #1266.