docs: cp over a running AppImage is NOT reliably safe (appimagelauncherd) - #37
Merged
Merged
Conversation
…erd) Corrects the 2026-05-31 claim. Witnessed 2026-06-04: cp at 17:17 triggered appimagelauncherd desktop re-integration at 17:17:33; the running instance was cleanly terminated at 17:17:48 (systemd scope end, no segfault, no kernel trace; user confirmed they did not quit). The same swap had survived twice on 2026-06-02 — non-deterministic. Also promotes --config.npmRebuild=false from investigation candidate to field-proven safe-build path (3 successful builds with the instance live).
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.
Corrects invariant #2 after the 2026-06-04 incident: the
cpto ~/Applications can trigger an appimagelauncherd desktop re-integration that cleanly terminates the running instance (no segfault — systemd scope end 15 s after the swap; user confirmed they did not quit). Survived twice on 2026-06-02 → non-deterministic → treat the cp as the disruptive step. Also promotes--config.npmRebuild=falseto field-proven (3 live builds).🤖 Generated with Claude Code