Check out our Monthly Survey Page to see what our users are running.

Fedora 33 released with lots of improvements to the Linux desktop

By - | Views: 15,433

Sponsored by Red Hat, the Fedora Linux distribution has today released Fedora 33 which brings in numerous improvements for desktop users.

For desktop users, Fedora Workstation is what you're looking for if you want what they claim is a "just works" Linux experience. Fedora 33 pulls in GNOME 3.38 'Orbis' which by itself is a pretty big upgrade, see our previous overview on that here. They're also now using the BTRFS filesystem as the default, which is again quite a major change that includes lots of advanced features for those who want it but for desktop users it shouldn't be a noticeable change. The Fedora team mention that the switch to BTRFS is laying the foundation to build upon in future releases.

Pictured - a fresh test install of Fedora 33.

This release also brings in an animated background (based on the time of day) by default which is pretty slick looking. As part of Fedora's "First" mission they try to include all the latest and greatest software and with Fedora 33 you get the likes of Python 3.9, Ruby on Rails 6.0, and Perl 5.32 as default. In their KDE edition, they've also enabled the EarlyOOM service by default to improve the user experience in low-memory situations.

If you make use of the Wine compatibility layer, this release should also now use the Direct3D to Vulkan translation layer DXVK as the default instead of wined3d which should give much better performance in Windows games run through it. As after we covered the proposal, it was approved. Fedora 33 ships with Wine 5.20 and DXVK 1.7.2.

You can see the release announcement hererelease notes here and download from here.

Article taken from GamingOnLinux.com.
24 Likes, Who?
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG, Humble Store and Paradox Interactive. See more here.
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
21 comments
Page: «2/3»
  Go to:

tmtvl 27 Oct
Quoting: Luke_NukemopenSUSE has been using it by default for years. It works fine and is a lifesaver with snapper and the ability to boot previous snaps.

Quoting: shorbergopenSUSE have done done it for a few years now, seems to generally work fine. It is also better tuned to be used as a default for the general masses than ext4 these days since it allows things like checksumming, compression, snapshots and copy-on-write while still being a widely used and integrated system compared to say ZFS.

I would like to third this argument plus add that being able to turn off COW in btrfs submodules is really useful for stuff like /var.
Quoting: tmtvl
Quoting: Luke_NukemopenSUSE has been using it by default for years. It works fine and is a lifesaver with snapper and the ability to boot previous snaps.

Quoting: shorbergopenSUSE have done done it for a few years now, seems to generally work fine. It is also better tuned to be used as a default for the general masses than ext4 these days since it allows things like checksumming, compression, snapshots and copy-on-write while still being a widely used and integrated system compared to say ZFS.

I would like to third this argument plus add that being able to turn off COW in btrfs submodules is really useful for stuff like /var.
If I had a cow it would probably be useful to be able to turn it off.
vipor29 27 Oct
thinking about giving this a shot
Arehandoro 28 Oct
I (usually) love fedora, and I love the changes introduced in 33. But the post, and comments so far, seem to miss the most important and controversial changes this iteration includes (for me); systemd-resolved as a default dns daemon.

For other complaints; I'm still waiting on docker fixing cgroup2 or having podman-compose on a production level capability.
omicron-b 28 Oct
Quoting: ArehandoroI (usually) love fedora, and I love the changes introduced in 33. But the post, and comments so far, seem to miss the most important and controversial changes this iteration includes (for me); systemd-resolved as a default dns daemon.
What's wrong with it?
I believe I have it in Ubuntu 20.04, but I use stubby and DoT, so it was as simple as about 2 lines in terminal to switch to stubby.
Truth be told, stubby may actually crash about once a month and I have to restart it to get back to Internet.
Maybe I need to learn how to use systemd-resolved after all.


Last edited by omicron-b on 28 October 2020 at 2:44 am UTC
wvstolzing 28 Oct
Quoting: omicron-b
Quoting: ArehandoroI (usually) love fedora, and I love the changes introduced in 33. But the post, and comments so far, seem to miss the most important and controversial changes this iteration includes (for me); systemd-resolved as a default dns daemon.
What's wrong with it?
I believe I have it in Ubuntu 20.04, but I use stubby and DoT, so it was as simple as about 2 lines in terminal to switch to stubby.
Truth be told, stubby may actually crash about once a month and I have to restart it to get back to Internet.
Maybe I need to learn how to use systemd-resolved after all.

Various compatibility issues: https://pagure.io/fesco/issue/2476
I used it for a while on Arch; FWIW I thought the configuration was really tidy & simple -- though I had to switch back because *some* application -- can't remember what for the life of me, sorry -- kept breaking.
jens 28 Oct
View PC info
  • Supporter
Quoting: ArehandoroI (usually) love fedora, and I love the changes introduced in 33. But the post, and comments so far, seem to miss the most important and controversial changes this iteration includes (for me); systemd-resolved as a default dns daemon.

For other complaints; I'm still waiting on docker fixing cgroup2 or having podman-compose on a production level capability.

Do you know the current status of docker and cgroups2?
I use docker quite frequently, Fedora32 sets the needed kernel arguments for still having support for older cgroups when installing docker. I guess this is still the same with Fedora33?
omicron-b 28 Oct
Quoting: wvstolzing
Quoting: omicron-b
Quoting: ArehandoroI (usually) love fedora, and I love the changes introduced in 33. But the post, and comments so far, seem to miss the most important and controversial changes this iteration includes (for me); systemd-resolved as a default dns daemon.
What's wrong with it?
I believe I have it in Ubuntu 20.04, but I use stubby and DoT, so it was as simple as about 2 lines in terminal to switch to stubby.
Truth be told, stubby may actually crash about once a month and I have to restart it to get back to Internet.
Maybe I need to learn how to use systemd-resolved after all.

Various compatibility issues: https://pagure.io/fesco/issue/2476
I used it for a while on Arch; FWIW I thought the configuration was really tidy & simple -- though I had to switch back because *some* application -- can't remember what for the life of me, sorry -- kept breaking.
Thank you for reply, tested systemd-resolved on Ubuntu 20.04 and DoT just fails with my selfhosted server:
$ dig youtube.com 

; <<>> DiG 9.16.1-Ubuntu <<>> youtube.com
;; global options: +cmd
;; connection timed out; no servers could be reached

Same server works via systemd-resolved without DoT, port 53, with DoT via stubby, port 853 and with DoT via my router, 192.168.Х.Х. port 53 (but I'm not always at home, so I set up DoT also on laptop).
Will try once again on Ubuntu 22.04 I guess
Arehandoro 28 Oct
Quoting: jens
Quoting: ArehandoroI (usually) love fedora, and I love the changes introduced in 33. But the post, and comments so far, seem to miss the most important and controversial changes this iteration includes (for me); systemd-resolved as a default dns daemon.

For other complaints; I'm still waiting on docker fixing cgroup2 or having podman-compose on a production level capability.

Do you know the current status of docker and cgroups2?
I use docker quite frequently, Fedora32 sets the needed kernel arguments for still having support for older cgroups when installing docker. I guess this is still the same with Fedora33?

Not really. Not long ago I saw some issues on GitHub and seemed that they were being worked on, but no offical word on this.

Haven't upgraded to f33 yet, need to find some spare time at work first :D
Diable 29 Oct
Quoting: dpanterBTRFS as default on a desktop distro... guess we'll find out how that experiment turns out before long.

It's been stable for every day use for a while now. It's just the whining of edge cases users and the anti-Facebook crowd has been drowning out it's achievements. If all goes well we'll see the other big distro switch as well.
While you're here, please consider supporting GamingOnLinux on:

Patreon, Liberapay or PayPal Donation.

We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register

Or login with...
Sign in with Steam Sign in with Twitter Sign in with Google
Social logins require cookies to stay logged in.

Livestreams & Videos
Community Livestreams
Latest Forum Posts