When will my Fedora KDE 41 upgrade to 42?

Ask Fedora
, ,
1

I already made a KDE 42 USB for another computer that needs linux.

I wonder tho, hours after Fedora KDE 42 released, when will my already installed Fedora PCs get to upgrade to 42?

I just want to know that “nothing wrong has gone on behind the curtains”, for any reason.
I know that the 15th was an early release because “it was ready early”, but I don’t know more than that.

2

Only when you trigger it manually (from Discover or the command line): Upgrading Fedora Linux to a New Release :: Fedora Docs

1 Like
3

Schermata_20250415_230557
Schermata_20250415_2305571920×1080 408 KB

I was gonna say “I swear the popup isn’t there tho, I’d’ve noticed it”, but then just now I got some minor updates and the popup upped its pop.

Thanks,
it’s just that I’m a little nervous/paranoid as a person.

4

:smiley:

Interesting, I can’t see it in Discover yet. Maybe they stagger the notification to avoid everyone downloading at once.

btw is that a mistranslation in the Discover screen… “non è disponibile” ?

5

An update for F41 suddenly appeared on Discover but something weird was going on in the terminal. I ran:

sudo dnf upgrade --refresh
Nothing to do.

dnf check-update
Showed all the updates from Discover.

sudo dnf upgrade
Nothing again.

So I just ran it from Discover instead. After a restart which was needed, Discover now shows F42 available. I think I’ll wait awhile tho.

6

Those commands wouldn’t upgrade you to a new version, just give you the latest F41 packages.

To upgrade to F42 from the terminal you need different dnf commands, as per this howto.

7

That’s what I’m saying. I wanted to get the latest F41 packages but the upgrade command couldn’t find them.

8

Ah sorry, I see.

I saw this myself in the past in fact - it can happen because PackageKit (which Discover uses) has a different cache than dnf: KDE Discover shows package and kernel updates that dnf does not

1 Like
9

But how could dnf check-update see the new packages which sudo dnf upgrade --refresh couldn’t? Is it possible that these two commands rest on different versions of dnf and, therefore, rely on different metadata?

10

They do have different caches (the sudo command uses root’s cache, the non-sudo command uses your user account’s). (For example: Reddit - The heart of the internet)

However, your situation doesn’t seem the same as the one in that Reddit post. root’s cache shouldn’t be out of date in your case, because you used --refresh in your first sudo command.

So I don’t know!