Guard omitted fcitx5 and bt-agent user units - #106
Open
Fail-Safe wants to merge 1 commit into
Open
Conversation
The trimmed ARM64 guest enables these Omarchy units without shipping their binaries, so fcitx5 Restart=always floods the journal with 203/EXEC. Skip both units with ConditionPathExists until the packages are installed. Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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.
Summary
ConditionPathExistsdrop-ins foromarchy-fcitx5.serviceandbt-agent.serviceso units enabled by Omarchy's first-run script stay inert when their binaries are absent from the trimmed ARM64 guestFixes #91
Problem
The guest materializes and enables
omarchy-fcitx5.service, butfcitx5is not in the factory package set. WithRestart=always/RestartSec=2, the unit 203/EXEC-loops and can dominate the journal.bt-agent.servicehas the same binary gap; it only stays quiet today because/sys/class/bluetoothis missing in the VM.Approach
Match the idiom already used by upstream
omarchy-tailscale-receive.service: guest-side drop-ins underetc/systemd/user/*.service.d/withConditionPathExistson the ExecStart binary. Installing either package later makes the existing enabled unit start normally.Test plan
python3 -m unittest discover -s guest/tests -p 'test_*.py'python3 guest/tests/verify.pysystemctl --user status omarchy-fcitx5.serviceshows skipped/condition rather than restarting; journal no longer floods with 203/EXECfcitx5and confirm the unit becomes startable without changing the drop-in