I think part of the other problem is that Linux, in general, is meant for servers. So if anything functions, keep on chugging and rely on external monitoring to alert the user. Only acknowledge failure when all hope is lost.
Which is great for a server, not so much for a desktop where you might realize kde plasma fell over at 15:22 because you can’t click to a new window and the clock hasn’t updated since then (in fairness, I expected that when I finally installed openrazer). Nothing a reboot can’t fix but it still makes debugging a lot more tedious.
Not sure of a good way to handle it, but it would be wonderful to get stuff like that sooner rather than needing to wait for a full on kernel panic catastrophe.
And, in fairness, when I have to deal with a windows PC I have definitely noticed that MS changes the frequency of blue screens a lot from year to year. Back in the day, even a slightly wonky mouse driver would instantly trigger one. Then sometimes it feels like every single service could fail and it still wouldn’t pop one.
Linux recently DRM (Direct Rendering Manager, not copyright protection garbage) subsystem recently gained the ability to do something even better.
It can render a QR code containing debug information and kernel logs.
I actually had to use this not too long ago. I wasnt expecting a helpful html file generated by the qr code.
I love it when real information is given to users, instead of esoteric error codes that lead you to bullshit slop sites when googled.
https://github.com/markusfisch/BinaryEye
Default apps tend to suck at recognizing big codes.
Huh this is few kernel versions back. I haven’t had a kernel panic in years, will have to simulate one and see if fedora supports this.
Yeah. Heard about that, never seen it in action.
I think part of the other problem is that Linux, in general, is meant for servers. So if anything functions, keep on chugging and rely on external monitoring to alert the user. Only acknowledge failure when all hope is lost.
Which is great for a server, not so much for a desktop where you might realize kde plasma fell over at 15:22 because you can’t click to a new window and the clock hasn’t updated since then (in fairness, I expected that when I finally installed openrazer). Nothing a reboot can’t fix but it still makes debugging a lot more tedious.
Not sure of a good way to handle it, but it would be wonderful to get stuff like that sooner rather than needing to wait for a full on kernel panic catastrophe.
And, in fairness, when I have to deal with a windows PC I have definitely noticed that MS changes the frequency of blue screens a lot from year to year. Back in the day, even a slightly wonky mouse driver would instantly trigger one. Then sometimes it feels like every single service could fail and it still wouldn’t pop one.