Oh it was hard. FYI Fedora supports a major version for a year. To upgrade from non-supported old version, additional steps may be required:

• https://en.wikipedia.org/wiki/Fedora_Linux#Releases
• Can I upgrade from an End Of Life (EOL) release?

I hope you could solve the new issue too.

You won't HAVE to, but it might make it easier at first. The kernel module for the drivers simply needs to be signed and then secure boot will be happy. I've done it for debian before but can't find the exact piece of documentation explaining how to sign the kernel module.

Edit: Debian Guide

@senectus Why should it be more complicated than dnf group install […] and maybe dnf group uninstall […]?

The council!

If I were you I would ask in [email protected]

Silverblue has Firefox installed as an RPM.

There are multiple ways to add the missing codecs, the easiest one is to add the rpmfusion RPMs, reboot and install libavcodec-freeworld.

So I suppose you have the Flatpak AND the RPM installed. I would recommend the Fedora RPM, it works great and is really fast.

Also, you get more answers on discussion.fedoraproject.org

The Signal one will just be a metadata issue.

flatpak update -y
kill -9 gnome-software
pkcon refresh

Checking inside /usr/lib/kernel/install.d/, you can see the mechanisms in place for installing new kernel entries. Not knowing what you did to your config (did you back it up before making changes?), you should check if the entries are being populated properly in /boot/loader/entries/. If they are, you have likely toyed with the BLS config in some way that broke being able to load dynamic entries without mkconfig.

If that is indeed the case, I wouldn't know exactly what you touched to break it, but this discussion forum might give some insight.

If this isn't the problem, it might be helpful to post your grub config minus any sensitive details to help determine what is going wrong.

The main ublue variants (bluefin/aurora, bazzite) use ublue-update for updating.

This fixes many issues like not updating on metered connections or on low battery.

Have a look in there, maybe you can hook a notify-send -t 0 -a "Update" "Update finished" "reboot any time to apply them"

The -t 0 makes the message stay there forever until clicked. Otherwise you can enter a number in seconds.

You could also open a PR in their ublue upate. They dont want update messages as normies never update manually. So a config could enable this message opt-in.

You may find more help on https://discussion.fedoraproject.org

First: please mention "I am dual booting the Fedora KDE spin with Windows" at the top, to make things clearer :)

But lets see.

1.

It's e the time in my BIOS is correct.

Dont understand that sentence. But this may be a typical windows thing, as Windows is changing the BIOS time to the one used, while Linux normally keeps the BIOS time normal and uses the offset (like UTC+3).

Have a look at this page, ItsFoss is awesome

timedatectl set-local-rtc 1

2.

This sounds like a KDE Wallet issue.

Under systemsettings, see your KDE Wallet settings. Do you have a wallet set as default, that was created by default?

The default wallet uses your login password and gets opened with the login from SDDM. If you changed your login password, or something else, this doesnt work.

In the network settings, did you select "save password for this user (encrypted)" or "save password for all users (unencrypted)"? For wifi passwords you could use that as a fallback, its actually more secure in some scenarios afaik, as only plasma can read it.

3.

You are using an nVidia card, did you install any drivers? Nvidia didnt care for linux way too long. You may want to install them manually.

As your system is fresh, and as you need Nvidia drivers, I highly recommend switching to universal blue. Their kinoite-nvidia image has all the drivers and settings, and if something breaks, it is at their end and you will not get the update.

I really cant recommend some hacky way to install the drivers, blacklist nouveau, enable the drivers etc.

ublue.it

I use kinoite-main daily, it is awesome. Atomic/image based Fedora is way better.

Note though that dualbooting is not as easy it seems.

• guide 1
• some dude even triple boots with Haiku

(The rpm-ostree variants are now called "Atomic Desktops" but not long, in the past the GNOME "Fedora Silverblue" was the most dominant)

4.

Linux Mint uses legacy boot and is not secureboot compatible. Fedora should actually cause less problems.

Search on Fedora Discuss, this is also a common problem with a fix.

5.

Discover only shows graphical apps, you install it from the Terminal (Konsole).

But as I said, I do not recommend installing NVidia drivers on your own on Fedora, as it has too many updates and sometimes drivers break. This happens way too often.

Also to use them you will need to make some more small changes to some files, it is not complex but a few steps.

I recommend kinoite-nvidia by ublue, or as ublue has this as their main variant, Aurora:

https://getaurora.dev/

I think a lot of these problems (time settings, etc.) are because of Windows.

Maybe get a second drive and install Aurora or Bazzite on that.
Nvidia drivers and other stuff is included ootb and Fedora Atomic images always were way smoother than the KDE spin in my experience.

1. If you dual-boot into Windows, that's probably what sets the time. Linux expects the time in the BIOS to be set to UTC by default, Windows does not. You can change some registry entry in Windows so it uses UTC as well.

2. Might be related to 5.

3. Discover is (mostly) for GUI applications. Follow this guide to install the NVIDIA driver.

@Enragedzeus @possiblylinux127 It semms like you are confusing Fedora 38 with 39.

The best. Checkout the rpm-ostree variants.

• see all official atomic desktops
• all ublue images
• community images

A few things Fedora centers itself around:

• Wayland-oriented Workstations
• SELinux support OOTB
• BTRFS as default filesystem
• General attitude toward using close to bleeding edge packages as defaults
• Package order of Fedora rpm repos, Fedora Flatpak -> RPMFusion, Flathub -> copr -> external installation
• Immutable variants of Fedora exist for the major desktops

Fedora generally prides itself on being a Wayland-focused and oriented workstation distro. There is still active support for desktop environments/window managers that run on Xorg, but you should consider moving toward a Wayland-supporting environment (Gnome, KDE, Sway, Hyprland).

SELinux (a Mandatory Access Control system) is enabled by default and has pretuned policies installed that should support most use cases out of the box. SEApplet is a useful utility to find active SELinux denials in case an application is getting permission denied issues for seemingly no reason.

If you intend to use BTRFS as your filesystem of choice and want to utilize it to its fullest (encrypted partitions, subvolume encryption, automatic snapshots), it is best to read up how BTRFS and subvolumes work before partitioning so that your subvolumes will be correct the first time. It can be tedious to edit subvolumes, move their contents, and remount portions of the filesystem after they have already been populated.

I'm sure you're used to how things on Arch with bleeding edge works, and understand that on Arch you should always read patch notes before updating. Generally, updates on Fedora are fine to just push through. It is worth generally reading what is new when performing system upgrades to a new version of Fedora, I have noticed occasionally in over five years of usage the first target release of a new version of Fedora can sometimes have breakages that tend to get fixed within the next couple of weeks. There is extensive testing for system upgrades that can be openly viewed, but the testing doesn't always catch everything before a new release.

By default, the best way to grab packages on Fedora is from the official repos or from the Fedora Flatpaks. Barring that or if you aren't satisfied by a default package for whatever reason (some stuff in default repos doesn't have ffmpeg support or others due to codec licensing issues), you can add the second-party RPMFusion repos or add Flathub to grab additional or alternative packages as well. If those avenues fail, you might be able to find someone maintaining the package you need or want to test on Copr, which is essentially like Ubuntu's Launchpad PPA platform. Barring all else, you could manually install a given application externally, though obviously this typically isn't the best solution in most cases. Some cases where you might want RPMFusion packages are for things like audacity-freeworld, which includes proper ffmpeg support for Audacity. This package comes from rpmfusion-free. Or you might want something like akmod-nvidia to install the proprietary NVidia drivers or steam to install Steam. These packages come from rpmfusion-nonfree. Also, if you are not familiar with Flatpak, it might be worth becoming familiar with how it works (Flatseal is an excellent application that lets you modify how certain Flatpaks are sandboxed).

Immutable variants of Fedora (Silverblue, Kinoite, Sway Atomic, Budgie Atomic) also exist and provide an immutable base image that won't typically get modified across boots. Most of the custom user installation of programs is intended to be installed via Flatpaks (Fedora or Flathub) or through using toolboxes to create sandboxed environments for certain workflows. If you absolutely need to rebase the system image with extra utilities, rpm-ostree is available to modify the system package selection, though this method is not recommended to just be used to install everything (needless rebasing of the immutable image defeats the point of using an immutable distro). Obviously these spins aren't for everyone, but are there for those who want to use them.

My first two concerns are: -I can't find any software that can manage my NZXT 240 correctly I found Cooler Control which depends on liquidctl But there's an open ticket that won't be solved right away. -I have a problem with Falthub, I have the Fedora dependences but it's not up to date compared to what you can find on Github. -Gwenview or Gthumb don't want to play my videos.

And I have other worries but for the moment that's all I have in mind

This is the best summary I could come up with:

After not being ready in time for this week's early release target date, it's now been determined today that Fedora 40 is ready for release next week.

At today's Go/No-Go meeting, it was determined that Fedora Linux 40 Final RC1.14 meets all the release criteria with no blocker bugs remaining and thus declared a "GO" for release next week.

Fedora 40 thus will see its official release happen next Tuesday, 23 April.

Fedora Linux 40 features the GNOME 46 desktop components, the shiny new KDE Plasma 6.0 desktop will be available, the Linux 6.8 kernel is powering this beast, and a plethora of software package updates like LLVM 18 along with various exciting features.

Meanwhile set for release next Thursday, 25 April, is the Ubuntu 24.04 LTS release.

A busy week ahead for Linux distributions and more Phoronix benchmarks to come.

The original article contains 141 words, the summary contains 141 words. Saved 0%. I'm a bot and I'm open source!

This is the best summary I could come up with:

The Fedora Engineering and Steering Committee (FESCo) on Monday approved some last-minute features ahead of the Fedora Linux 40 release quickly coming up in February.

• A new tool for Fedora IoT called "Simplified Provisioning" that makes it easier to deploy and configure the Fedora Internet of Things (IoT) edition.

• Fedora IoT will now be built using the RPM-OSTree unified core.

• As for the recent debate around Fedora 40 dropping KDE X11 by default, FESCo has offered their latest guidance.

At the meeting they decided that KDE packages may reintroduce support for X11 are allowed in the main Fedora repositories but that they must not be included by default for any release-blocking deliverables like the ISO/image, etc.

More details on this week's FESco rulings can be found via the Fedora mailing list.

The original article contains 269 words, the summary contains 134 words. Saved 50%. I'm a bot and I'm open source!

check the GRUB_CMDLINE_LINUX key in /etc/default/grub it should contain the info about any subvolume. if it does not then there might be another grub config hook that is used by Fedora to add that info. If you want to be able to change subvol names without having to touch the grub config you might also want to switch to using subvolid instead of subvol keys on the kernel command line, because the id will stay the same after a rename (this could backfire though if you assign functions to certain names like "fallback" etc.).

Edit: found the hook that adds the kernel command line option for btrfs subvolumes. in /etc/grub.d/10_linux there is this bit of code:

case x"$GRUB_FS" in
    xbtrfs)
        rootsubvol="`make_system_path_relative_to_its_root /`"
        rootsubvol="${rootsubvol#/}"
        if [ "x${rootsubvol}" != x ]; then
            GRUB_CMDLINE_LINUX="rootflags=subvol=${rootsubvol} ${GRUB_CMDLINE_LINUX}"
        fi;;
    xzfs)
        [skipped for brevity]
        ;;
esac

so it seems it is always looking at the subvol name of the currently mounted root fs.

1. Does Silverblue being immutable has an effect on security, or is it more about stability and reliability?

It should also be more secure. The fact that your install is the same as thousands of others, including the devs', and that updates get patched as a whole, makes it more secure due to the reproducibility you mentioned. If the devs notice a flaw, it will also be on every other install and fixed immediately.
In theory, malicious actors also can't modify the (live) system, but I can't make a statement about that.

You can also take a look at SecureBlue if security is very important to you.

Updates get installed automatically and staged, so you can just boot into a fresh and updated image every day when shutting off the PC before bed without even noticing :)

2. Is it possible to have Nvidia drivers with Secure Boot on Silverblue, and how?

Go to universal-blue.org and select your wanted image there. They have a Nvidia-image for every variant, where the drivers are already baked into the base image.

They support Secure Boot, and if the driver breaks, which it shouldn't, because then thousands others would do that too, you can just select yesterday's image and don't have to worry about fixing something. Your OS will always boot and be usable!

Take a look at my post for further information: https://feddit.de/post/8234416

I use deja dup because I have a lot of useless (unencrypted) storage from organisations. Deja dup backs up my data in an encrypted and easy to use fashion. It is a gnome app but I use it in KDE.