First: please mention “I am dual booting the Fedora KDE spin with Windows” at the top, to make things clearer :)
But lets see.
--
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).
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.
--
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.
(The rpm-ostree variants are now called “Atomic Desktops” but not long, in the past the GNOME “Fedora Silverblue” was the most dominant)
--
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.
--
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:
Die Flüchtlingsbeauftragten der evangelischen und katholischen Kirche sprechen der CDU mit Blick auf deren Asylpläne christliche Werte ab. CDU-Generalsekretär Linnemann pocht auf das Gegenteil. Doch nun protestieren auch noch Hunderte Geistliche gegen die Christdemokraten....
I’ve been running Tumbleweed for a few years now. It’s great, but it’s not 100% autopilot, updates often require manual intervention (resolving small problems) or updates try to add 50 packages I don’t need (recommends) all the time despite them not being in a pattern. I’ve been looking for a distro on which I could...
I wasnt aware of how bad this situation was actually.
It started by me asking in their forum “where do I need to place a repo to add external RPMs”?
Because on Atomic Fedora the dnf repo add command doesnt work, but the repos can be placed in the same dir and work the same. So I assumed this worked on “the OpenSUSE equivalent” the same.
Instead of getting the needed answer (assuming that their model worked just as well as Fedoras) they told me
installing RPMs causes random changes to the system that are not reversible (yes they are, on Fedora)
installing RPMs is not supported, only Flatpaks (which dont support user namespace creation for process isolation in browsers, so not an option here)
the only RPMs that should be installed are drivers etc. So they advise something they dont support, lol
they supposedly hate Fedora?
I still dont know where such a repo would be placed, and why they would support installing RPMs on the “chaotic” traditional variants, while they dont on their “more stable” “immutable” variants.
Well yes I know. Because their model is not any better in solving the mentioned problems.
I mean, by logic, a better package manager should improve stability when installing system packages. You shouldnt need to install Flatpaks or Distrobox containers only on “immutable” distros, but especially on traditional, messy ones.
Because these traditional distros dont have measurements to revert the permanent changes that sometimes occur when installing, changing or upgrading packages.
If your OS is so unreliable that you only support installing Flatpak, then the package management is crap.
This is pretty complex and I wanted to write a post about it, will follow.
While OpenSUSE’s model may look similar to Fedora’s Atomic Desktops, it is not.
In short:
Fedora Atomic uses rpm-ostree for managing all installed RPM packages. This is basically git for binaries, meaning your system is 100% the system that Fedora tests and pushes to their servers.
Then you have the ability to add and remove RPM packages, which will be transparent (rpm-ostree status) and reversible (rpm-ostree reset).
This means
you can modify the system and install or uninstall any RPM you want
these changes will always be applied fresh to your system, meaning you will always start fresh and apply exactly them.
this means the entropy (amount of randomness, how much your system diverges from their system) is very little and transparent. “I cant reproduce on my system” is gone
you can switch (rebase) ostree remotes, also with support for container images like uBlue uses. This means you can have various upstream configurations with different goals, like Aurora/Bluefin, Bazzite etc
you can still reset your system to 100% upstream, to make sure you have reproducible bugs, or to find a broken package
Most of these things are not possible on OpenSUSEs model. To my understanding they basically just use zypper but with BTRFS snapshots. So you normally update the system, but into a new snapshot to the updates dont affect the current one.
But there is no way to reset or rebase, this means from day 1 there is a chance that your system is not the same as upstream.
They try to tackle that by advising to not install any RPMs which is pretty hillarious. If you use a good RPM distribution model like rpm-ostree, installing or even removing packages is no problem because A: you see the changes transparently and B: you can always reset.
As good as their efforts may be, their reproducible builds, their services, their YaST etc. Their “immutable variants” are not the same and way worse.
You can also see that by the adoption of rpm-ostree I would say. OpenSUSE has microOS and Aeon, which dont share a common name and are separate projects. Kalpa, the KDE Plasma variant, is officially unmaintained.
Fedora has
Atomic Desktops: GNOME, KDE, Sway, Budgy
uBlue: Bluefin, Aurora, Bluefin-DX, Aurora-DX, Bazzite (and all its variants), dozens of base images for various hardware and desktops
Apart from the other comment explaining the many benefits of rpm-ostree to transactional-update (apart from the horrendous name)
it creates BTRFS snapshots between normal zypper updates. So you can have the benefits of offline updates without having to wait at boot or at shutdown.
You are referring to standard Fedora here. Atomic variants have no offline update screen.
Also just having snapshots between updates means you cannot rebase to the updated AND vanilla variant.
You could make a BTRFS snapshot right after install and keep that from disappearing. But this means when you need to reset, you downgrade tons of packages wich always causes problems with config files etc.
Just like silverblue, the concept is to try to install everything through flatpak/distrobox and avoid adding anything unnecessary to the base, so that system updates can be snappy and unproblematic.
As said in the other comment, I dont think this is specific to Atomic Fedora. For sure the long rpm-ostree updates kinda enforce that (they get way longer when layering packages) but rpm-ostree is way more stable than for example Ubuntu APT or Fedora DNF. So I think you should use Flatpak and Distrobox on the traditional distros, while Atomic Fedora is actually less critical.
“Immutable” OpenSUSE is not any better than mutable OpenSUSE though, their package manager doesnt solve many problems with installing random RPMs to the base. So it needs Flatpaks etc more.
I was really tired of opening my laptop, updating everything and then rebooting. I just want to open my pc, have all updates automatically applied in the background through systemd units so that the next time I boot, I have an updated system. No “updating” during next boot.
This is all standard Fedora. Atomic Fedora updates in the background and reboots are as fast as normal ones.
But there are some issues with just updating automatically:
using tons of data when connected to a phone hotspot
As far as I understood their package manager is just zypper with enforced snapshots.
It is not layering, it is just installing like regular. There is no base, no image, just the base packages that are managed traditionally. This will just add another package and there is no way to revert it
Updates are atomic, but they are not reproducible, as there is no real base. You cant just use rpm-ostree status, reset and install the layered packages, as there is no reset. There is no way to revert back to the currently shipped base OS. You can only revert back the snapshots that were created every update, so you could keep a snapshot of the fresh install, and that would be somewhat a reset, but reset to completely outdated packages, causing likely dotfile conflicts etc.
The OS is always atomic and snapshots are enforced, changes have to be made to the next deployment / BTRFS snapshot and the live base system is read only afaik.
There is no rebase. And Kalpa is officially unmaintained. And there are no other variants than the 2 :/
Inefficient data usage is a problem. Network connections arent free, there are people using metered networks, or with really bad bandwidth.
I am really interested in improving this.
I dont agree with “atomic distros are the future” as in my eyes Fedoras approach is the only good one really (and even that has tons of issues, see here).
Some things need to be improved:
flatpak runtimes share tons of packages but each gets downloaded individually, even though they may be deduplicated locally
podman containers just for installing packages dont need a separate system, it would be perfectly fine if they would just use a symlinked or otherwise deduplicated base system.
rpm-ostree has no delta update support, but afaik Fedora neither
So it may be worth the tradeoff for us both, but I definetly see a problem and I am also kinda tired of using podman containers for something they are not supposed to (system upgrades are impossible for example).
I want to experiment with the “linking all the system binaries to a podman container”, the flatpak stuff needs to be solved by them.
This is due to the fact that Kalpa is a traditionally package-managed OS. On image based Atomic Fedora there is a base image, and the overlays are always added on top.
If these overlays are always the same, like ublues “hardware enablement” then it makes way more sense to use the base image and apply these changes once. Doing that workload once, minimizing randomness between users and doing unstable stuff like proprietary NVIDIA drivers, rpmfusion, custom kernels etc. on a single repo. The issues will occur there and can be fixed centrally.
The slow process it not ostree, but doing the changes on every update. But tbh when updates are automatic it doesnt matter than much anymore.
Updating and rebooting before using is basically just paranoia. And Atomic Fedora now has automatic updates (by default, was just a settings switch before).
I also disagree with some Fedora devs that “development should be done in containers”. This works well for apps, but results in duplication and does not allow editing the OS itself.
Snapshots are a lot more flexible. You can make any modifications to your system without issue.
The issue is the lack of any versioning and control. It works “without issue” just as it works on traditional distros, it works until suddenly you have strange errors, devs tell you “I cant reproduce this here and btw modifying the base OS is not a supported use case” (it actually isnt) and as there is no way to revert the “issueless changes” you need to fix them manually or reinstall the OS.
Yes I have. I think they do the same as OpenSUSE microOS basically.
The live system is immutable, when updating they clone it to the other partition and run regular apt in there. (Not sure about that but I think). Same issue as on OpenSUSE [whatever they want to call these variants].
It sounds like the thing Android is doing, but in detail it is way less secure. I only know of rollback prevention and signing, so an update needs to be an update and cannot downgrade components. This may not be available there but idk.
And the entire boot process on any Linux distro is extremely insecure compared to Android/GrapheneOS on a Pixel.
Their “apk package manager” is just a wrapper for Distrobox, not solving any fundamental problem. But Distrobox for sure is awesome for closing the gaps.
I think uBlue with homebrew is doing something more sustainable here though, as homebrew is independent, well maintained (cross OS!) and does not rely on having a separate OS run in parallel. So if you imagine Fedora would only supply base packages in some future, a project like homebrew could take care of the rest.
Also I couldnt even get the Debian version installed in a Qemu VM, same as with EndlessOS, so yeah so much about “alternative immutable distros”.
I’m using Debian 12, Ryzen 7 5700X processor, and Radeon HD 5450 graphics card. I have tried uninstalling and reinstalling VLC but it didn’t resolve the issue. Here’s an excerpt from the VLC’s log file:...
Auf dem Rückweg von einer Veranstaltung zu ihrem Fahrzeug sei die Bundestagsvizepräsidentin Katrin Göring-Eckardt (Grüne) von Demonstranten bedrängt worden. Das Auto mit Göring-Eckardt und ihrem Fahrer sei auch an der Abfahrt gehindert worden. “Mehrere Personen schlugen dabei in aggressiver Stimmung auf das Fahrzeug”,...
Various issues with Fedora 40 KDE spin
Hi all,...
Firefox Power User Keeps 7,400+ Browser Tabs Open for 2 Years (www.pcmag.com)
Protest beim Parteitag: 700 Pfarrer sind wütend auf die Asylpläne der CDU (www.n-tv.de) German
Die Flüchtlingsbeauftragten der evangelischen und katholischen Kirche sprechen der CDU mit Blick auf deren Asylpläne christliche Werte ab. CDU-Generalsekretär Linnemann pocht auf das Gegenteil. Doch nun protestieren auch noch Hunderte Geistliche gegen die Christdemokraten....
Which file system do you recommend for Linux?
Just a simple question : Which file system do you recommend for Linux? Ext4…?...
NASA remotely reprogramming Voyager 1 also means that aliens can reprogram all of our satellites.
NASA remotely reprogramming Voyager 1 also means that aliens can reprogram all of our satellites.
There are songs we've gone our whole lives without hearing and the best song we've ever heard might still be out there.
deleted_by_author
The future of desktop Linux might be like OpenSUSE Kalpa/Aeon
I’ve been running Tumbleweed for a few years now. It’s great, but it’s not 100% autopilot, updates often require manual intervention (resolving small problems) or updates try to add 50 packages I don’t need (recommends) all the time despite them not being in a pattern. I’ve been looking for a distro on which I could...
[Resolved] After updating through both APT and the Software Store, I can't play mp4 videos with VLC anymore. The screen goes blank for a second or two then the audio starts playing without the video..
I’m using Debian 12, Ryzen 7 5700X processor, and Radeon HD 5450 graphics card. I have tried uninstalling and reinstalling VLC but it didn’t resolve the issue. Here’s an excerpt from the VLC’s log file:...
Demonstranten bedrängen deutsche Bundestagsvizepräsidentin: Polizei ermittelt wegen Nötigung (www.tagesschau.de) German
Auf dem Rückweg von einer Veranstaltung zu ihrem Fahrzeug sei die Bundestagsvizepräsidentin Katrin Göring-Eckardt (Grüne) von Demonstranten bedrängt worden. Das Auto mit Göring-Eckardt und ihrem Fahrer sei auch an der Abfahrt gehindert worden. “Mehrere Personen schlugen dabei in aggressiver Stimmung auf das Fahrzeug”,...