The desktop image was the first image we made, and that same install is what Bazzite is still built on today :)

Only the kernel module is open source, and it’s just a wrapper for closed source blobs.

In actuality the open source drivers just kill all support for the 10 series, and otherwise do nothing to fix Nvidia’s utterly fucked up driver problems.

Bazzite lead developer here, we actually never used the flatpak. Our first release had it installed in a distrobox container on the desktop images. Deck images always had RPM Steam because Steam is essentially functioning as a desktop environment there. We moved them both to be RPM for support consistency reasons.

Smells like FUD to me.

It’s the same RPM that’s installed in workstation from RPM fusion. There’s nothing custom about that.

Gamescope is also an RPM, it’s a slightly newer version than what Fedora packages but it’s packaged the exact same way. Neither of those are likely to break because they are fundamental to the basic functionality of the deck images.

Additional pre-installed packages are added, but existing packages are not touched.

It’s immutability comes directly from silverblue and kinoite, again nothing custom there.

Such as?

I’m not sure what you mean by that, it’s directly built on Fedora which is probably one of if not the best workstation OS.

The very first release was actually a steam deck release, the desktop release came later.

I read the complaints and I lost all respect. I will not be spending another cent with that company, nor will I attend any of his future talks.

I am very ashamed that I own a single wolfire title.

Gamescope is broken on Nvidia and has been for years.

It currently breaks Firefox, but they’re working on it.

Bazzite doesn’t use flatpak steam. Standard rpm install with no sandboxing.

If you installed it that’s entirely your fault.

For me it’s foldables, those have come a long way in a short time and I find them to be very compelling.

Once they perfect it though it’s going to be back to the same stale shit.

No the article you are replying to, lay off the crack.

As evidenced by: this article

Oh wait

Your use case works

We build twice a week, that’s not frequent enough for a web browser.

Ultimately it’s saving you from yourself, if this bug gets fixed and there’s a way I can unfix it, I will do so.

If you need RPM Firefox, my recommendation is that you install it with Distrobox. This also solves the security issue that we remove upstream Firefox over - update frequency.

You don’t want Firefox to only update when your operating system image does. As far as I’m concerned the bug preventing Firefox from being re-added is a feature.

I opted for Lutris because Bottles has issues that make it unrecommendable and unsupportable by us.

Because it’s only shipped as a flatpak (They bullied the Fedora packager until they quit) it doesn’t support the frame limiter built into gamescope on the deck images (Requires a patch in Mesa).

As a contributor to the Northstar mod for Titanfall 2, we originally wanted to recommend it as the default Linux install path due to it’s friendly UI, but found because it avoids using winetricks it’s missing required dependencies. Despite us trying to work with them and contributing code, to this day it still doesn’t work, and recent discussions about this problem were extremely abrasive from their side, much like the above linked issue.

Ultimately Lutris provides a more consistent experience for gamers that are already used to Steam - with the same tools working for both. That’s my reasoning anyway.

As far as wine, we only install wine-core and not the entire stack, that’s purely for Lutris dependency reasons and isn’t intended to be used by the end user. Wine-ZGUI for instance is a Flatpak, and Lutris will install its own copy of wine - most likely Wine-GE or a derivative.