Describe the bug
When attempting to install Bazzite using the recommended Web-based ISO image (bazzite-nvidia-open:stable), selecting the "Install to hard drive" option results in an infinite loading screen/hang with the message waiting for 127.0.0.1. The web-based installer backend/frontend communication appears to fail completely.
Right before this hang occurs, the installer displays a prompt warning that a Windows BitLocker partition has been detected on the system, stating that it might interrupt the installation process. Clicking "Yes, I'm aware, continue" triggers the infinite waiting for 127.0.0.1 loop.
This issue is persistent and has been reported by other community members since at least February (similar case documented in Discord: https://discord.com/channels/1072614816579063828/1074422586894712912/1471860376302780579).
Additionally, inside the Live ISO environment, attempting to launch Firefox results in an immediate crash right after opening.
What did you expect to happen?
What did you expect to happen?
The Web-based installer should successfully initialize the local loopback server connection after dismissing the BitLocker warning, open the GUI layout, and allow the user to proceed with the OS installation.
Firefox should launch successfully in the Live environment without crashing.
Session Logs
i will add later when start Bazzite again
Hardware
CPU: Intel Core i5-14600K
GPU 1: Intel Raptor Lake-S GT1 [UHD Graphics 770]
GPU 2: NVIDIA GeForce RTX 5090 (GB202)
RAM: 126 GB
Storage Configuration:
sda: 3.6T
sdb: 115.5G (Live USB)
nvme1n1: 931.5G (Target drive for Linux)
nvme0n1: 3.7T (Windows drive with BitLocker enabled)
Extra information or context
Image Build: 44.20260515
Image Name: bazzite-nvidia-open:stable
Urgency Note: The Bazzite website currently states: "The Legacy installer will be phased out soon, using the regular installer is recommended." Because the regular (web-based) installer is completely broken phasing out the Legacy Anaconda installer will leave some users completely unable to install Bazzite. This makes fixing the web-installer loopback bug a high-priority issue.
Additional Info: The system has a multi-drive configuration where one of the secondary drives (nvme0n1) contains a Windows installation encrypted with BitLocker. The target drive for Bazzite (nvme1n1) is completely separate and unencrypted, meaning BitLocker shouldn't block the installation, yet the web-installer environment crashes or freezes immediately after scanning the storage layout and throwing the BitLocker warning.
Describe the bug
When attempting to install Bazzite using the recommended Web-based ISO image (bazzite-nvidia-open:stable), selecting the "Install to hard drive" option results in an infinite loading screen/hang with the message waiting for 127.0.0.1. The web-based installer backend/frontend communication appears to fail completely.
Right before this hang occurs, the installer displays a prompt warning that a Windows BitLocker partition has been detected on the system, stating that it might interrupt the installation process. Clicking "Yes, I'm aware, continue" triggers the infinite waiting for 127.0.0.1 loop.
This issue is persistent and has been reported by other community members since at least February (similar case documented in Discord: https://discord.com/channels/1072614816579063828/1074422586894712912/1471860376302780579).
Additionally, inside the Live ISO environment, attempting to launch Firefox results in an immediate crash right after opening.
What did you expect to happen?
What did you expect to happen?
Session Logs
Hardware
CPU: Intel Core i5-14600K
GPU 1: Intel Raptor Lake-S GT1 [UHD Graphics 770]
GPU 2: NVIDIA GeForce RTX 5090 (GB202)
RAM: 126 GB
Storage Configuration:
Extra information or context
Image Build: 44.20260515
Image Name: bazzite-nvidia-open:stable
Urgency Note: The Bazzite website currently states: "The Legacy installer will be phased out soon, using the regular installer is recommended." Because the regular (web-based) installer is completely broken phasing out the Legacy Anaconda installer will leave some users completely unable to install Bazzite. This makes fixing the web-installer loopback bug a high-priority issue.
Additional Info: The system has a multi-drive configuration where one of the secondary drives (nvme0n1) contains a Windows installation encrypted with BitLocker. The target drive for Bazzite (nvme1n1) is completely separate and unencrypted, meaning BitLocker shouldn't block the installation, yet the web-installer environment crashes or freezes immediately after scanning the storage layout and throwing the BitLocker warning.