Update with a fedora 44 package gave my pc problems to boot

Ask Fedora
1

this morning i found a couple of updates, one of them mentioned fedora 44 and was like a couple hundred megabytes of size together with other updates, i let it download and then i pressed the button to update and reboot, the system installed the packages and then stood in a black screen with no signal to my tv at all

after like 3 minutes it said it didnt found a boot drive or something like that, i pressed the reset button and it did something similar, i turned off my pc by turning off the psu

when i turned on the psu and then the pc again, it booted normally and now i cant find the package it said it installed

i just installed feora 43, i saw th fedora 44 package and imagined it was a distro upgrade or something, i was ready to reinstall from the liveusb!

what did i do wrong?

2

Where did you find them?

3

discovery warned me about them, i entered discovery, marked download all updates and then rebooted pc to finish the process

4

The command below shows any output?
$ dnf list --installed | grep -i fc44

5

nothing, i had to remove the $ because with it it says instruction not found

6

flatpak list --runtime | grep 44 would also be interesting, to see if you have any Fedora Flatpaks using a Fedora 44 runtime.

7

Fedora Platform org.fedoraproject.Platform 44 f44 fedora-testing system
Mesa org.fedoraproject.Platform.CL.default f44 fedora-testing system
Mesa org.fedoraproject.Platform.GL.default f44 fedora-testing system
fedoraproject plataforma traducciones org.fedoraproject.Platform.Locale f44 fedora-testingsystem

i dont remember adding any testing repos but i needed some flatpaks added some months ago, perhaps i added those there

8

I would prefer to format that as

dnf list --installed | grep -i fc44

Not everyone knows the old convention of prefixing command by ‘$’ or ‘#’ to symbolise the prompt and the super-user prompt respectively.

9

Are you sure it is “org.fedoraproject.Platform” instead of “org.freedesktop.Platform”? either way it seems came from flatpak.

10

You might be able to find the source of it using flatpak history | grep "add remote" .

However, installing these new Flatpak runtimes is not likely to be the cause of problems booting the system. At worst you might get strange behaviour when running the Flatpak apps, but not at boot time.

The “other updates” might have been the cause of the issue you saw.

1 Like
11

I disagree, I had seen several commands that needed root without the author mentioned this and without sudo.
It’s a convention when we see the meaning of “$” or “#” prompt.
If they don’t know Linux conventions then they should take Linux 101 Basics!

12

And where would new Linux users find this documented?

1 Like
13

people here are aggressive and disrespectful, i should go back to win 11, so i dont have to read this

14

On the whole, we are pretty good, and nearly always aim to be.
Sorry that a little bit of ‘infighting about meta-discussion’ has put you off.
You were smart enough about the commands to figure it out yourself.

Stick with us a while, trust me, it’s no reddit here.