If you installed Bazzite without any obvious issues, then rebooted only to land on a blank black screen with no way to interact with the system, you are not alone. This is a fairly common problem, especially when booting into Game Mode for the first time. The good news is that you do not need to reinstall your system. In this guide, we will walk you step by step through how to fix Bazzite getting stuck on a blank screen in Game Mode.
Takeaways:
- Learn how to fix a Bazzite system that will not boot into the GUI.
- How do you fix blank/black screen boot issue in Bazzite?
Table of Contents
Getting Into the Hidden Grub Menu
Before doing anything else we'll first need to enter the hidden Grub Menu.
- If Bazzite has already started loading, you have missed Grub.
- Restart the machine with CTRL+ALT+DELETE.
- As it powers back on, start pressing Escape.
- When you land in the BIOS, open the Boot Menu.

- Select Fedora, press Enter, then quickly press Escape again.

- If timed correctly, this drops you into the Grub menu.
How to Fix a Bazzite System That Will Not Boot Into the GUI
From the Grub menu:

- Press e to edit the boot entry
- Scroll down to the line that starts with linux
- Press End, then press Space and type 3

- Adding 3 tells the system to boot into multi user mode instead of the graphical interface.
- Now press CTRL+X or F10 to boot with this temporary configuration.
- Instead of the GUI, you should land in a terminal login screen.
- Log in with your normal username and password. While typing your password, nothing will appear on screen. That is normal.

Unhiding Grub for Easier Access
Once inside the terminal, it is a good idea to make Grub visible by default.
- Run:
ujust --choose

- Search for the Grub option and select configure Grub, then choose to unhide it.

- Enter your password when prompted.
- Now reboot:
reboot
- On the next startup, Grub should appear automatically. No more frantic Escape key timing. Just remember there is a countdown timer, so press the arrow keys quickly if you want to edit an entry.
Booting the KDE Desktop Manually
If your system was failing because of Gamescope, you may still be able to start the desktop manually.
- Repeat the earlier steps to edit the Grub entry and append 3 to boot into the terminal.
- After logging in, try starting KDE directly:
/usr/bin/startplasma-wayland
- You can press Tab to autocomplete.
If the issue was limited to Gamescope, this may boot you straight into the KDE desktop even though the default graphical session was failing.
Rolling Back to a Working Bazzite Image
- Bazzite includes a rollback helper tool.
- If you know a specific release works, you can rebase to it:
bazzite-rollback-helper rebase
- For example, if a fix was included in version 40-20240427, select that image and confirm with y.
- The system will begin rebasing to that version.
Here's a full guide on roll back methods: How to Roll Back to a Previous Version of Bazzite
Watching Rebase Progress (Not Required but Interesting)
During a rebase, there is no visible progress in the main TTY. To monitor activity:
- Press CTRL+ALT+F2
- Log in again
- Run:
journalctl -f -u rpm-ostreed

This shows live logs from the rpm-ostree service. You will see download chunks and progress updates, confirming that the process is active.
- To return to your original session, press CTRL+ALT+F1.
- When the rebase finishes, reboot and select the updated image from Grub. In most cases, this restores your system to a working state.