Skip to content

Update log is written to /tmp and lost on reboot #4965

Description

@amanat361

Problem

omarchy-update-perform writes the update log to /tmp/omarchy-update.log. When the update includes a kernel upgrade, omarchy-update-restart triggers a reboot, which wipes /tmp. The log is lost before the user can review it.

Suggestion

Write the log to ~/.local/state/omarchy/update.log instead. That directory already exists and is used for migration state and toggles. It survives reboots and follows XDG conventions.

The change is one line in bin/omarchy-update-perform:

# before
exec > >(tee "/tmp/omarchy-update.log") 2>&1

# after
exec > >(tee "$HOME/.local/state/omarchy/update.log") 2>&1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions