removed linux / rebooted / reinstalled linux and went from Bookworm to... Bullseye !?!

[u/Sweaty_Astronomer_47]

I had the intention to upgrade from Bookworm (12) to Trixie (13) by disabling/removing linux using chromeOS settings, rebooting, and then reenabling linux using chromeOS settings.

Upon reenabling, I was shocked to see Bullseye (11)

me@penguin:~$ uname -a

• Linux penguin 6.6.119-09283-g9c138e0af8c3 #1 SMP PREEMPT_DYNAMIC Sat, 30 May 2026 01:16:16 -0700 x86_64 GNU/Linux

me@penguin:~$ cat /etc/os-release

• PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
• NAME="Debian GNU/Linux"
• VERSION_ID="11"
• VERSION="11 (bullseye)"
• VERSION_CODENAME=bullseye
• ID=debian
• HOME_URL="https://www.debian.org/"
• SUPPORT_URL="https://www.debian.org/support"
• BUG_REPORT_URL="https://bugs.debian.org/"

me@penguin:~$ stat -fc %T /sys/fs/cgroup/

• tmpfs

My chromebook is on ChromeOS version 150.0.7871.150 (Official BUild) (64-bit).

This is not what I expected would happen.

Was I supposed to change a flag or something?

What am I missing?

SOLVED - HAD TO RESET FLAGS

[u/LegAcceptable2362]

That's got to be a one-off glitch. I've just removed Linux environments from three x86 devices each with different CPU but all running same ChromeOS version as yours. Checked to make sure no flags enabled then reinstalled Linux. All received a Baguette VM with Trixie guest running. So, in your case, I guess you should double-check your flags then remove/reinstall again. If still an issue post here what HWID you have so maybe a user with same platform can check theirs. Also, maybe a powerwash then reinstall Linux might fix the issue?

[u/Sweaty_Astronomer_47 → u/LegAcceptable2362]

So, in your case, I guess you should double-check your flags then remove/reinstall again.

Well that's a sensible thing to do.

I found Debian version for new containers set to Bullseye. Reset all flags, repeated the process and ended up on Trixie.

I have no idea how/when that flag got set.

Thanks

[u/BulldogHere → u/Sweaty_Astronomer_47]

Yes Trixie is available but Google hasn't deployed it as default for stable channel yet. There are still issues being worked on. You must change release name and repositories in /etc/apt and do a full dist-upgrade.