Hello Arch Linux Community, I’m sharing an incident with my Arch Linux installation in case it proves useful for future investigations or helps identify similar issues.
Yesterday, I explored several AUR repositories, reviewed issues, and worked on contributions. I submitted pull requests for some and stored local copies of others in /tmp for investigation. Today, I updated my Arch Linux system and installed Waydroid. The system appeared to function normally before restarting. After the restart, Arch Linux no longer booted. Selecting Linux Boot Manager from my HP laptop’s UEFI boot menu immediately returns me to the firmware startup menu. I never reach the LUKS2 password prompt. System details: - Distribution: Arch Linux - Hardware: HP laptop - Disk encryption: LUKS2 - Boot mode: UEFI - Recent activity: AUR repository investigation and contributions, system update, Waydroid installation - Hardware diagnostics: SSD, memory, and other tested components passed Given my recent work with AUR repositories, I considered whether an unsafe package or script might be involved. However, I have no evidence of malware or an AUR compromise, and I cannot establish any connection between those activities and the boot failure. The cause could instead involve the update, EFI bootloader, or another component. I cannot currently access the installation to retrieve logs or investigate further. I’m not requesting troubleshooting assistance; I’m sharing this as an unconfirmed boot failure report for informational purposes, in case it becomes relevant to future reports. Thank you.
