Skip to content

omamobile-omarchy 0.1.44: /run is 0755 before Omarchy 4.5's migrations run - #673

Merged
derekross merged 1 commit into
mainfrom
omarchy-run-0755
Nov 12, 2026
Merged

derekross merged 1 commit into
mainfrom
omarchy-run-0755

Conversation

@derekross

Copy link
Copy Markdown
Owner

Found by the round 52 review of #670.

The problem

Omarchy 4.5 refuses to work under a /run anyone can write. Its sudo migration (1788163635) exits 1, which stops omarchy update, and its pacman hooks abort later transactions (#447). Boot images from before #437 mount /run 1777.

With Omarchy pinned at 4.5.0-3 (#670):

  • A 7 Pro installed from release 2026.11.08 gets 4.5 and omamobile-device-cheetah 0.1.51 in one update. The new boot image is written to slot B, but the phone is still running the old one, so the update stops at that migration. A restart and a second update finish it, and nothing says so.
  • Every other phone stops at each attempt until its owner rebuilds and pushes boot images with initramfs: mount /run 0755, not tmpfs's default 1777 #437: the 7 Pro's is the only device package that carries boot files.

The 7 Pro that took the update on 2026-11-11 had the new boot image pushed first, so it didn't show this.

The fix

/usr/lib/tmpfiles.d/omamobile-run.conf: z /run 0755 root root. pacman's own tmpfiles hook (PostTransaction) applies it in the transaction that installs it, before Omarchy's migrations run, and systemd-tmpfiles-setup applies it at every boot, on every device, whatever the boot image.

Tested

On the Pixel 7 Pro, Omarchy 4.5.0-3, uname -r 7.3.0-rc6-omamobile-g1a9d1d4e9289:

/run omarchy_security_assert_root_directory /run 755
set to 1777, as an old boot image leaves it refuses
after systemd-tmpfiles --create with this file: 755 root passes

A 0700 directory inside a scratch /run keeps its mode. test/run-mode.sh checks the staged rule, and the mode change where it can run as root.

Not run: a whole update from 4.0.6 on a phone booted from an old boot image.

Refs #447.

🤖 Generated with Claude Code

…s run

Omarchy 4.5 refuses to work under a /run that anyone can write: its sudo
migration (1788163635) exits 1, which stops omarchy update, and its
pacman hooks abort later transactions (#447). Boot images from before
#437 mount /run with tmpfs's default, 1777. A phone gets a new boot
image only through a restart, and only the Pixel 7 Pro's device package
carries one, so with Omarchy pinned at 4.5.0-3 (#670) a release-installed
7 Pro stops in its first update to 4.5 until it is restarted and updated
again, and every other phone stops at each attempt until its owner
rebuilds and pushes boot images. The 7 Pro that took the update on
2026-11-11 had the new image pushed first, so it didn't show this; the
round 52 review of #670 found it.

A tmpfiles.d rule, z /run 0755 root root. pacman's own tmpfiles hook
(21-systemd-tmpfiles.hook, PostTransaction) applies it in the transaction
that installs it, which is before Omarchy's migrations, and
systemd-tmpfiles-setup applies it at every boot, on every device and
whatever the boot image.

On the Pixel 7 Pro (Omarchy 4.5.0-3): with /run set to 1777, Omarchy's
omarchy_security_assert_root_directory /run 755 refuses; after
systemd-tmpfiles --create with this file /run is 755 root and it passes;
a 0700 directory inside a scratch /run keeps its mode. Not run: a whole
update from 4.0.6 on a phone booted from an old image.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@derekross
derekross merged commit 3699d0e into main Nov 12, 2026
2 checks passed
@derekross
derekross deleted the omarchy-run-0755 branch November 12, 2026 00:53
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…s run (derekross#673)

Omarchy 4.5 refuses to work under a /run that anyone can write: its sudo
migration (1788163635) exits 1, which stops omarchy update, and its
pacman hooks abort later transactions (derekross#447). Boot images from before
derekross#437 mount /run with tmpfs's default, 1777. A phone gets a new boot
image only through a restart, and only the Pixel 7 Pro's device package
carries one, so with Omarchy pinned at 4.5.0-3 (derekross#670) a release-installed
7 Pro stops in its first update to 4.5 until it is restarted and updated
again, and every other phone stops at each attempt until its owner
rebuilds and pushes boot images. The 7 Pro that took the update on
2026-11-11 had the new image pushed first, so it didn't show this; the
round 52 review of derekross#670 found it.

A tmpfiles.d rule, z /run 0755 root root. pacman's own tmpfiles hook
(21-systemd-tmpfiles.hook, PostTransaction) applies it in the transaction
that installs it, which is before Omarchy's migrations, and
systemd-tmpfiles-setup applies it at every boot, on every device and
whatever the boot image.

On the Pixel 7 Pro (Omarchy 4.5.0-3): with /run set to 1777, Omarchy's
omarchy_security_assert_root_directory /run 755 refuses; after
systemd-tmpfiles --create with this file /run is 755 root and it passes;
a 0700 directory inside a scratch /run keeps its mode. Not run: a whole
update from 4.0.6 on a phone booted from an old image.

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
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.

1 participant