Bazzite February Update

New: Smaller Images

Bazzite is now bult with DNF5. This is part of our transition to full bootc, and has allowed us to pull 600MB out of all images without affecting functionality. It also grants us the ability to remove some packages we previously weren’t able to. Starting with today’s update, Wine is no longer part of the image (But this does not affect Lutris or Steam in any way). Additionally, Konsole is now fully removed from KDE images as I have been promising for months now. In both cases distrobox or flatpak can restore this functionality if needed for your personal workflows.

Ultramarine Collaboration

As of this release, Bazzite is now using the Terra repository for some packages. This also means your favorite Bazzite changes may make their way to Ultramarine’s offerings. Please give a huge thank you to that team for being willing to host these packages and work with us on bettering the Linux desktop.

Latest Nvidia Drivers

As of this release we are now running 570.86.16 for both open and proprietary variants!

Bug Fixes

Lastly, a huge number of minor bugs have been fixed. This includes sleep issues, issues affecting the Legion GO S, and many, many more. Be sure to let us know what you think!

9 Likes

Is this why my image builders has been failing? Or is it just GitHub free image builder being GitHub free image builder as usual? I recall I had to change some url stuff a week or so ago, now it’s just an issue with no space left for building the image (for some reason).

This only hit stable today, doesn’t sound related if you’ve been having this problem for weeks.

I installed org.winehq.Wine from Discover after applying the February update. Now wine does not find the executables anymore. For instance, a program that ran just fine using wine has the following error:

bazzite@bazzite:/var/home/bazzite/.wine/drive_c/MiniPro$ flatpak run org.winehq.Wine ‘C:\MiniPro\MiniPro.exe’
wine: failed to open “C:\MiniPro\MiniPro.exe”: c0000135

When installing it asked for system or user. Should I have installed it for user?

Or is the problem that it does not have the WINEPREFIX environment variable (i.e. WINEPREFIX=/home/bazzite/.wine) I set the environment variable prior to executing the command.

Note: This is a big change for anyone that has programs configured to use wine, and some additional explanation is needed.

If you check our previous advice and support forums you will find that we have been extremely consistent on telling people to never use system wine under any circumstance.

Since you’ve already made it part of your workflow what you can do is remove the flatpak you just installed and then install wine-core in a fedora distrobox. This will behave the exact same way as the previous install did.

Well I tried one last thing. I reinstalled the application using the flatpak command and the Windows installer and it worked.

Since I currently only have one wine program it is okay for me.

I spoke too soon. The application runs but the interface does not detect the USB device. There is an error on the installer that says “DPInst.exe does not execute on your current Operating System.” I did not get this error before.

So can I uninstall and reinstall wine for user.? That is not a problem for me. Or should I install wine-core in a fedora distrobox as you said before?

If you really need system-level wine and don’t want to use a wine frontend, then use a Distrobox container for sure.

I am a new user and now have to figure out how to do a Distrobox container. :slight_smile:

Bazzite’s guide: Distrobox - Bazzite Documentation

:angry::-1:

This is just stupid. A native KDE terminal not available on KDE disto because of… what?.. few megabytes of space?

We’ve been using a hacky solution to remove Konsole for over a year now, this change means you can layer Konsole without a workaround or use the flatpak.

Konsole is gone because Ptyxis is better. We prefer the container integration.

I understand the motivation for removal as I’ve been reading about it on other forum topics but I’d like to voice my dissatisfaction never the less.

Ptyxis being better is subjective, it certainly is not better for me, and one can assume there are other people thinking the same. On the other hand, I don’t see any problem in having them both.

Having to do the extra work to install the de facto default KDE terminal reminds me so much of IE and it being just a nuisance until you install a proper browser :unamused:

Having both is either problematic to new users because having two apps that do the exact same thing is a bad look, or problematic to experienced users because you have to undo our workaround to properly use your terminal of choice.

This is best of both worlds. We get the experience we want for our users, and you can do whatever you like after the fact without us getting in your way.

4 Likes