Huh. I should check again

It doesn’t work for me on SwayWM, maybe KDE does something else under the hood?

Edit: lol Sorry, I mistook xrandr for brightnessctl. (I had aliased xrandr brightness change commands to “brightness” in my shell)

brightnessctl doesn’t work with Wayland

I don’t think there is anyone like that. Being normal is way too abnormal.

Holy shit, I can do that too. I noticed just now because of your comment.

Thank you for unlocking my new power.

That saves 100% money, but it’s like the least healthy way to live…

Thanks for the suggestions, I will try again as soon as I can

If it’s too much of a headache, I can just wipe the partition and install something else, or just reinstall fedora I guess.

Yes, I updated the release targets first.

The device can resolve dns requests. I can browse freely and normally.

I’m specifying the release server manually as directed in the fedora docs for upgrading editions. That’s what I followed

Well the thing is, I’ve done this exact same opertaion on my own machine. It has managed to hold stable from F38 to F42.

But I’ve had to deal with similar annoyances since when I installed it on this particular laptop.

I decided Fedora since I use it myself, so I figured it’d be easier to debug. I think I’ll pave the install and replace it with debian based mint if nothing works (I’ve made a separate partition for critical files)

When you say you did it manually, what do you mean exactly?

I meant that instead of doing it the “safe” GUI way, I simply did it by CLI, with the instructions available at the fedora docs