-
Amazon Deals - ToS - Like us?
Fedora Updates
- Thread starter amish
- Start date
- Replies 41
- Views 11,646
Fedora 20 released & fedora project completes 10 years
https://lists.fedoraproject.org/pipermail/devel-announce/2013-December/001282.html
https://lists.fedoraproject.org/pipermail/devel-announce/2013-December/001282.html
OMG! We’re at forty! (Announcing the release of Fedora Linux 40) - Fedora Magazine
Announcing the release of Fedora Linux 40 with a description of it's contents, features, and improvements.
I was using Fedora KDE for sometime and was happy with it. But Fedora 42 turned out to be a disaster. Apparently, it has a bug that crashes your system within 5 minutes of boot. Fedora developers don't seem concerned and people are left to investigate and find workarounds which don't work for everyone. Nobody even knows what is causing the crash. Hence, I have switched to Manjaro which has been working fine so far.
Haha, this made me check what version of Fedora I'm running, and sure enough, it's 42... I guess I'm in the lucky category for whom it has been rock stable. Current uptime is 1 week since I installed updates, otherwise, the previous uptime was 5 weeks and it was working perfectly fine.
But yeah, that sounds so shitty :/
@Navjot Singh I am also using Fedora KDE since F38, but not facing any shutdown issue as you.
In F39 there was a issue in Intel vPro CPU code in Kernel which led to soft lock, but was patched by the Intel maintainers after sometime.
Then last week I had Plasma Shell crashing two times, but it seemed to be a Plasma issue.
Beyond that it has been a smooth ride.
Any clue from
Fedora can only merge patches from upstream, beyond that distributions can't really do anything.
Can you link any discussions on this ongoing issue.
In F39 there was a issue in Intel vPro CPU code in Kernel which led to soft lock, but was patched by the Intel maintainers after sometime.
Then last week I had Plasma Shell crashing two times, but it seemed to be a Plasma issue.
Beyond that it has been a smooth ride.
Any clue from
dmesg what was causing shutdowns, to me it seems to be a Kernel or Plasma problem.Fedora can only merge patches from upstream, beyond that distributions can't really do anything.
Can you link any discussions on this ongoing issue.
Google Fedora 42 crashes and you will come across tonnes of posts across their forums and Reddit. Some of them have linked the issue with the AMD CPU, which I do have and others claim it's a Plasma issue. I never even got the time to run any of the workarounds or gather any info, given how quickly it kept crashing on me.
For now, I can't tell you what the issue was since I have already switched. Maybe I will try again with 43.
For now, I can't tell you what the issue was since I have already switched. Maybe I will try again with 43.
It's a BTRFS (file system) corruption issue. Not a Fedora issue. Also affected other Distros using BTRFS and the specific linux kernel (6.15.X and 6.16.X) versions which triggered the corruption issue.
Anyway the fix is simple but the problem is you need live usb to run the command (sudo btrfs rescue zero-log) to fix it.
Also latest Fedora has fixed this issue. So if you have fedora which is still working just run the dnf update command and the new version will work without this issue.
Btw I am running dual boot with Fedora 42 and my laptop has AMD CPU and Plasma. But luckily I was not affected by this issue.
Similar threads
