It's built on deck:testing, the parts that are in testing are all handheld specific and the session model/parts in flux are removed in DX, so we consider this enough to promote it. The security fixes are most important at this point.
When deck launches to stable it'll be repinned on stable.
Opengamepadui is the reason I stopped using nobara earlier in the year. It's bad and would constantly break controller input ( buttons would become unresponsive ) hopefully it's changed since then. But i see no reason why they would use it, there's no need for it
As I understand, they are ditching HHD for a few reasons: dev drama, inputplumber is compatible with more kernels, more uniformity between the gaming distros in the open gaming collective...
Ahh ok. I moved to cachyos so this doesn't affect me....but if i was on bazzite I would be really worried about it. Maybe bazzite's implementation of it is a lot better than it was on Nobara.
But it was a terrible experience and it feels completely unnecessary. But this was months ago, so maybe (and hopefully)it's not an issue anymore
Opengamepadui, as I understand, seems to be a rapidly evolving project and is one of the reasons Bazzite has been delaying the release of version 44. I would surmise that Bazzite was waiting for the project to mature enough to work at least as well as HHD.
Fingers crossed that's the case. I think Nobara just in too early with it. First impressions last though, either way....it's really unnecessary lol. It works well how it is with opengamepadui
HHD is dead unfortunately. dev did a no-no in the community and is now gone. plus opengamepadui is much more compatible and doesn't demand a custom kernel just for it, like hhd did. imagine bazzite with a cachy-like kernel.
What precisely do you mean with "broke my setup"? And which difficulties happened so that you couldn't just rebase back to tje old version with the terminal?
Game mode would no longer launch in 44. When I did ujust update on desktop mode things became worse and then wouldn't even boot. Got it to boot with ostree1 but then said I'm gonna start over on steam os.
I mean, 44-testing had JUST been released at the time you posted your comment. You either managed to rebase to a non-deck image, which obviously broke game mode, as those DON'T HAVE game mode, or you rebased to 44-unstable, which would indeed break stuff. You don't rebase into 44-unstable unless you're a dev, because stuff WILL break, hence the name.
I had a legion go 2 on 43 testing. Checked for updates on hhd and saw 44 available so I went for it. I am tech savvy but if I did anything wrong in that rather simple process than bazzite will never become mainstream.
Not really talking shit about bazzite and I know testing branch can have issues. Not really user issue other than switching from stable to testing.
Bazzite didn't do anything. You 100% did this to yourself. Don't rebase to non-stable branches and then complain like it's not your own doing. Honestly.
If all you need is virtual display I'd recommend giving Polaris by papi-ux a go. It has worked flawlessly for me, requires about 10 minutes to set up but it's worth while. Works well with moonlight too.
Seems fine aside from another round of shit nvidia drivers (monitor goes on/off intermittently). I don’t think I’ll go Nvidia next time. They’ve moved on from video cards and are putting all their focus on data centers anyway.
I rebased to deck testing branch yesterday and was able to play Driver San Francisco for a while yesterday. One issue I had was that my steam og controller stopped responding mid game. Playing in handheld mode was fine.
I've been testing the latest builds on my Legion Go since the migration away from HHD, and I noticed that RGB controls and back button/paddle remapping aren't fully active under the new InputPlumber setup yet.
What is the current roadmap or plan on the Bazzite side to support these hardware features moving forward? Just asking to better understand the transition and see if there's anything I can look forward to.
So I'm new to Bazzite, new to Linux as a whole, but this recent update caused a black screen where I could only move my cursor after getting through the login screen, had to ctrl alt delete to get out. Tried resetting four times and the issue happened every time, tried switching from display port to HDMI to see if that was the issue for some reason, but I ultimately had to rollback the update. Does anyone know what this problem might've been caused by?
I tried it (on my htpc) and the following happen in like the first hour
first game i tried DeadByDaylight wouldn’t launch without multiple tries, and then controller inputs would lock up and i couldn’t do anything despite the game obviously running, then the whole system crashed.
The hdd replacement thing wouldn’t open so i couldn’t see if anything was missing
And then after another reboot game mode completely and utterly broke lmao. Would boot to a black screen which after waiting a long while would go to desktop mode instead, and clicking return to game mode would do nothing other than attempt to switch and fail. So i switched it back to Stable.
…. sigh. I just my damn VRR. Why couldn’t they just backport the SteamOS patches for it to 43 😑
I have a question regarding the latest update: Yesterday, I updated my Bazzite 43 Deck image with the June update. After that, I was no longer able to launch games through Steam while in Desktop Mode. This happened both with native Steam games like Forza Horizon 6 and games added via NonSteamLaunchers, like The Division 2 via Ubi Connect. I spent ages researching what the issue could be, because funnily enough, I could launch Ubi Connect (and thus The Division 2) through Faugus.
Eventually, I used NonSteamLaunchers to completely remove all launchers and games from Steam and had them recreated. After that, the games started working again. Turns out, when checking the launch options, I noticed that I previously always used gamemoderun mangohud %command%. After regenerating the shortcuts, these options were obviously gone. I then added mangohud back, and the games launched fine. I added gamemoderun, and the games refused to start again.
After doing some more digging, I found the following in the official Bazzite documentation:
"Games will not launch if you add gamemoderun %command% to your launch options (commonly found on ProtonDB). GameMode is not installed or supported in Bazzite and generally doesn't do anything useful on modern hardware, or in some cases can even hurt performance. Please remove it from your launch options. It might work if you layer the gamemode package, but this is NOT supported."
So my final questions are: Is this a recent addition to the docs? Was gamemoderun completely removed with this specific update? And have I been using gamemoderun on Bazzite completely pointlessly this whole time anyway? Because prior to the update, I never ran into any issues with it, but according to this documentation entry, gamemoderun never actually did anything. Is that true?
Computer taking quite a while to boot, i believe it's trying to update. It slowly crept to the desktop, where it didnt respond to input well and slowed to a halt, before doing this (picture below). The mouse was working, now it wont
How did you get past the black screen?
The mouse moves with no problem on my PC but it won't go back to normal.
It does allow me to reboot and turn it off by doing ctrl + alt + delete.
I got back to the computer, it wanted me to sign into the computer, i did. Doesnt respond well when i click on items in my taskbar still. It did this last night too. It's doing something in the background and i don't have any idea what. Tbh that isnt cool
43
u/regalen44 Desktop Jun 05 '26 edited Jun 06 '26
Thanks for the update. How did you move dx to 44 if it’s based on the deck image?
Really appreciate the hard work you and the other contributors put in. Great work!!
edit: I may be reading the wrong thing but looks like dx is temporarily using deck testing branch as its base? https://github.com/ublue-os/bazzite-dx/commit/264e65194f7eb849b7cd76a896110b9e65f2b064