Bazzite 45 has arrived in the unstable channel, and so far it’s been smooth sailing! I’ve put it through some hardware stress tests on my Legion Go 2 and even managed to squeeze in a little Witcher 3 Remastered without any issues!
Bazzite 45 is shaping up to be a great release, and we want your help making it even better.
Introducing the Bazzite Community Testing Program!
As Bazzite continues to grow, so does the variety of hardware our users rely on. Expanding our testing efforts helps us catch regressions, validate more devices, and stay connected to what matters most: our users.
To support this effort, we’re building a community of dedicated, trusted testers who can help shape the future of Bazzite and Linux gaming.
Here’s what’s new:
- Dedicated Bazzite-Testing channel - A place to coordinate testing activities, share findings, and collaborate with other testers.
- New testing-help forum - Dedicated threads for hardware enablement, regressions, and testing-related bugs.
- GitHub issue tracking - Confirmed issues will be documented on GitHub and tracked through our Bazzite Project Board, ensuring that important findings aren’t lost in Discord.
- All testing-help threads must have a corresponding GitHub issue.
- A brand-new Bazzite Tester role! - Complete with a shiny green badge to recognize the people contributing to our testing and QA efforts.
- This role is reserved for testers who consistently participate and follow our established testing processes. We want the badge to represent meaningful contributions to the project!
We’re introducing this structure now because we recognize just how much Bazzite has grown. Building a sustainable testing process today means we’ll be better prepared for everything coming tomorrow.
Want to Help Test Bazzite 45?
There are a few things to know before jumping in.
1. Pin your current working deployment.
Before rebasing to testing, we strongly recommend pinning your current deployment:
sudo ostree admin pin 0
This preserves your working deployment and gives you a reliable fallback if something goes wrong.
If you want to return to the stable releases of Bazzite, and remove the pinned deployment, use:
sudo ostree admin pin --unpin <deployment number>
You can find your deployment number with rpm-ostreee status -v
2. Rebase to the testing or unstable channel.
You can switch through the Bazzite Portal app or run:
brh rebase testing
or
brh rebase unstable
3. Help us keep testing organized.
GitHub is our source of truth for tracking issues.
- Threads in testing-help must have an associated GitHub issue.
- Threads without an issue will be removed to keep the forum organized.
- If you’re unable to create an issue yourself, we’ll work with you to get it done!
- Be sure to be clear and concise when making a github issue. List all pertinent information, such as your image details, logs, and your
rpm-ostree statusoutput, along with hardware specifications.
Help Shape What’s Next
We’re incredibly excited about the future of Bazzite and Linux gaming. With the community growing and new developments on the horizon, having a reliable group of testers is more important than ever.
And with exciting developments around anti-cheat support for Linux, our community testers could be among the first to help validate some truly game-changing improvements.
The next chapter of Bazzite starts with the community. Come help us build it!
Follow Our Progress
You can view our hardware and known issues list to see where we still need help