Back

If Fedora 40 had a headlining change, it might be @kde Plasma 6. The KDE SIG have brought over all the hard work from that community to give you a solid desktop experience from day 1.

We're also pushing technology forward by making this release Wayland-only, though X11 apps will still work!

Plasma 6 is also available for our Kinoite users.

Give the Fedora KDE 40 spin a try today!
https://fedoramagazine.org/whats-new-in-fedora-kde-40/

We are proud of the stable reputation that Fedora Workstation has built over the years. We hope to add to that with Fedora Workstation 40!

Workstation brings @gnome 46 to users with tweaks to the Settings and Files apps. You can now use Remote Login to connect to a computer even if it doesn't have an active session.

Learn about these quality of life improvements and more: https://fedoramagazine.org/whats-new-fedora-workstation-40/

Try Fedora Workstation 40 today!

Silverblue and Fedora Atomic users - here's a guide on how to rebase to Fedora 40.

The graphical example used is for Silverblue, but if you follow the terminal instructions they will work on any Fedora Atomic Desktop. Just pay attention to use the name of your variant where applicable.

If anything goes bad, you can rollback to Fedora 39. Additionally you can pin your current image if you need to go back after a few updates.

https://fedoramagazine.org/how-to-rebase-to-fedora-linux-40-on-silverblue/

Fedora IoT 40 got some cool under-the-hood changes.

First is that Fedora IoT now uses the unified core model, making them the last rpm-ostree variant to make the switch.
https://fedoraproject.org/wiki/Changes/Fedora_IoT_Unified_Core

CORRECTION: The bootable container image change did not end up making it in Fedora 40.
https://fedoraproject.org/wiki/Changes/Fedora_IoT_Bootable_Container

Don't forget about all of our other spins and labs that have also updated to Fedora 40.

For Fedora Spins we have
- KDE (or Kinoite)
- Xfce
- Cinnamon
- MATE
- i3
- LXQt
- LXDE
- SoaS
- Sway (or Sway Atomic)
- Budgie (or Budgie Atomic).
https://fedoraproject.org/spins/

For Fedora Labs we have
- Astronomy
- Comp Neuro
- Design Suite
- Games
- Jam
- Python Classroom
- Scientific
- Security Lab
https://fedoraproject.org/labs/

You have a lot of options, alright lol

@js @fedora @slimbook But we do have them. Fedora 40 is the first release with new nouveau and NVK stuff.

@Conan_Kudo @fedora @slimbook Hm, let me see what happens when I stop removing my 4090 from the PCIe bus. It used to just suck the battery within 45 min if I didn’t do that (vs. 6h+)

@Conan_Kudo @fedora @slimbook OK, so it already starts “well”:

A bunch of these:

[   27.985286] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff

Preceded by:

[   17.627524] nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes

Which, I guess, is expected, because it’s a laptop?

So, how do I use the card now? And will my 4090 actually be faster than the AMD iGPU? (Doubt it)

@js @fedora @slimbook Not sure, maybe @Lyude or @karolherbst would know?

@Conan_Kudo @js @fedora @slimbook @Lyude the first one should be fixed by a kernel update (at some point) and the second can be ignored. We should probably remove that message at some point.

@karolherbst @Conan_Kudo @fedora @slimbook @Lyude Can I do anything useful with it if it is a secondary GPU, as in, not connected to any display? Or is it non-functional anyway because of the first error?

@js @Conan_Kudo @fedora @slimbook @Lyude you can do OpenGL offloading via `DRI_PRIME=1` or explicit device selection via EGL extensions or inside Vulkan.

@adamw @fedora so the image swapping piece is correct, but phrasing the previous OStree implementation as managing packages and dependencies is wrong? I thought this update copied the uBlue implementation for updates with OCI containers.

@Joseph_of_Earth @fedora it was already the case with the previous ostree implementation that you just got a new image when you updated. and both the previous and new designs are ultimately built out of rpm packages behind the scenes. it's more that the image format has changed. @cgwalters can explain it best, I guess. :D

@adamw @fedora @cgwalters I thought before you would only download the parts of the image that actually changed and then a new image would be made locally by merging in the changes, whereas now you are literally pulling down a new image and booting from it. That's the difference between updates on Fedora Atomic vs uBlue right now - uBlue "updates" by pulling down the latest build of the image and switching you to that. Though Fedora IoT might be doing it a different way.

@Joseph_of_Earth @fedora well, I'm thinking about how it looks to the user. the user is not "managing independent packages and dependencies" in either case.

@adamw @fedora true true. I'll rephrase, just wanted to make sure I understood what was happening under the hood.

@Joseph_of_Earth @adamw @fedora high level I would consider them equivalent (it’s just a different transport mechanism for the same content, one being an OSTree repo served as files over http(s) and the other being an OCI container image in a registry). At a lower level an OSTree remote will only fetch the files that have changed, but will make many small http requests to do so. An OCI remote is chunked larger (limitation of number of layers a container can have) but will make fewer requests.

@GermanoMassullo @fedora @kde I'm glad to hear that! We work very hard to do that and maintain a high quality, reliable experience!

@Conan_Kudo @fedora @kde thank you very much for your commitment to Fedora KDE!