2026.6.4 qemux86-64 signal 11 segfault

Installation
1

Good morning, I have been using HA for a few years, on an old laptop, running Oracle VM Machine with HA inside it, 5gb ram, ive been stuck on 2025.9.1 OS for a while now, initially it was due to not enough space to update, I cleared out a bunch of my old manual backups I didnt need and I think I have space now, I have almost 4gb of free space now.

I used MCP and integrated Claude last week, and its awesome, however the issue im running into is I can't update to 2026.6.4, every time I try it looks like it takes, then rolls it back to 2025.9.1

ive been trouble shooting with Claude, and it found some old things that were outdated, I removed them, it thinks that there is something wrong with the rich library crashing in python 3.14. after much back and forth it suggested I post here:

Still the same signal 11 segfault and the rich/segment.py SyntaxWarning right before it. This is now 100% confirmed to be a crash in the core HA 2026.6.4 image itself — nothing to do with your config or custom components at all.

The rich library crashing under Python 3.14 is a bug in the HA 2026.6.4 release for the qemux86-64 architecture. This is actually a known issue.

Here's what I'd recommend at this point:

  1. Post on the HA forums at community.home-assistant.io — search for "2026.6.4 qemux86-64 signal 11 segfault" and you'll likely find others with the same issue, or you can post your logs
  2. Wait for 2026.6.5 or 2026.7 — patch releases usually come quickly when there's a widespread crash bug like this

Any HA wizards understand whats causing this? or something completely different that I overlooked?

greatly appreciate any insight!

2

Otherwise, if this isn't working in the UI, try the CLI version. Common tasks - Home Assistant Operating System - Home Assistant
Update to 2025.10. If it takes, update one month at a time to the next one and see if that works.
I'd have a fresh backup as I go.

3

I had been trying this from the terminal, and it didnt work, however when I went to the HA VM PC and did it on the window in there, its been working, ive been doing it month by month, almost current! thanks for this!

4

I can confirm the same issue on VirtualBox OVA on macOS (Mac mini, Intel, 16 GB RAM).

Environment:

  • HAOS 18.0 (upgraded from 17.3)
  • HA Core 2026.6.4
  • VirtualBox 6.1, OVA installation
  • macOS host

Symptoms:
HA Core crashed with signal 11 (SIGSEGV) at every startup attempt after upgrading to HAOS 18.0, including in safe mode. The same rich/segment.py SyntaxWarning: 'return' in a 'finally' block appeared in logs immediately before crashes.

Workaround:
Rolling back to HAOS 17.3 via os boot-slot A in the HA CLI resolved the issue immediately. HA Core 2026.6.4 now starts cleanly on HAOS 17.3.

This confirms the issue is related to HAOS 18.0 (likely the Python 3.14 / rich library combination) rather than the HA Core version itself, since the same Core version runs fine on HAOS 17.3.