Fix Waydroid's "Can't open /dev/anbox-binder: No such process" on Arch kernels built with rust-bindgen 0.73.1
Arch GitLab packaging history (API) shows upgpkg: 7.2.3.arch1-3: rust-bindgen 0.73.1 rebuild on 2026-09-06 and upgpkg: 7.2.4.arch1-2: rust-bindgen 0.73.2 rebuild on 2026-09-08, and the same pair for linux-lts 6.18.49-3 and 6.18.50-2. waydroid/waydroid#2411 quotes the exact two log lines and the symlink, shows the rust_binder_open oops, links rust-bindgen#3406 (a struct layout bug), and has users confirming 7.2.4.arch1-2 and 6.18.50-2 fix it. stable-mirror.omarchy.org core.db, downloaded today, still lists linux-7.2.3.arch1-3 and linux-lts-6.18.49-3, and this machine's mirrorlist points there. All four archive URLs in the fix return HTTP 200. /usr/bin/omarchy-update-pacman-guard only blocks a transaction carrying both S and u, so pacman -U passes. linux depends only on coreutils initramfs kmod. waydroid#2422 is open with the ENOSPC report. Nothing was installed.
A kernel from the archive is newer than the rest of the frozen Omarchy snapshot and has not been tested against it. pacman will report local is newer until the mirror catches up. Keep linux-omarchy installed as a fallback, and do not reboot until dkms status shows your modules built for the new kernel.
Symptom
Waydroid initialises the binder nodes but never gets further. These two lines repeat forever:
[gbinder] ERROR: Can't open /dev/anbox-binder: No such process
Failed to add presence handler: None
/dev/anbox-binder exists as a symlink to /dev/binderfs/anbox-binder, so the node is there. Some machines also log a kernel oops in rust_binder_open. It started with linux 7.2.3.arch1-3 (or linux-zen 7.2.3, or linux-lts 6.18.49-3), and booting an older kernel works. On Omarchy 4.0.4 this is what you hit after switching from linux-omarchy back to the stock kernel to get binder.
Cause
Arch rebuilt its kernels against rust-bindgen 0.73.1 on 2026-09-06 (upgpkg: 7.2.3.arch1-3: rust-bindgen 0.73.1 rebuild, and the same for linux-lts 6.18.49-3). That bindgen release generates a wrong struct layout (rust-lang/rust-bindgen#3406), so the in-kernel Rust binder driver reads from the wrong offsets and open fails with ESRCH. Arch rebuilt against 0.73.2 on 2026-09-08 in linux 7.2.4.arch1-2 and linux-lts 6.18.50-2, and Waydroid works again from those builds (waydroid/waydroid#2411). Plain Arch got the fix with the next normal upgrade. Omarchy 4 does not. Its packages come from stable-mirror.omarchy.org, a frozen snapshot that as of 2026-10-04 still serves linux-7.2.3.arch1-3 and linux-lts-6.18.49-3, so omarchy update reports nothing to do.
Fix
**Plain Arch:**
sudo pacman -Syu
pacman -Q linux # 7.2.4.arch1-2 or newer
Then reboot.
**Omarchy 4:** the clean fix is to wait for the stable mirror to move, then run omarchy update and check pacman -Q linux. To get Waydroid working now, install the rebuilt kernel from the Arch Linux Archive. Install the matching headers too, or DKMS modules (NVIDIA included) will not build for it:
sudo pacman -U \
https://archive.archlinux.org/packages/l/linux/linux-7.2.4.arch1-2-x86_64.pkg.tar.zst \
https://archive.archlinux.org/packages/l/linux-headers/linux-headers-7.2.4.arch1-2-x86_64.pkg.tar.zst
dkms status # every module installed for 7.2.4-arch1-2
pacman -U carries no -S/-u pair, so Omarchy's pacman guard allows it. The kernel package depends only on coreutils, initramfs and kmod. Make sure linux boots first (see waydroid-no-binder-on-linux-omarchy-kernel for the BOOT_ORDER line in /etc/default/limine and sudo limine-update), then reboot.
linux-lts users can do the same with linux-lts-6.18.50-2 and linux-lts-headers-6.18.50-2 from https://archive.archlinux.org/packages/l/.
A separate Rust binder fault remains open upstream: large transactions fail with rust_binder: Failure in copy_transaction_data: ENOSPC (waydroid/waydroid#2422). It shows up under load rather than at startup, and no fix in a released Arch kernel was confirmed while writing this.
Verify
uname -r shows 7.2.4-arch1-2 or newer. waydroid session start reaches Android with user 0 is ready, and journalctl -b | grep -c 'No such process' stays at 0.
Sources
- https://github.com/waydroid/waydroid/issues/2411
- https://github.com/rust-lang/rust-bindgen/issues/3406
- https://github.com/omacom/omarchy/issues/12149
- https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/commits/main
- https://gitlab.archlinux.org/archlinux/packaging/packages/linux-lts/-/commits/main
- https://github.com/waydroid/waydroid/issues/2422