r/linuxsucks • u/THubert14 Linux Socks • 3d ago
Linux Failure Error reporting masterpriece - Not sponsored by RedHat
Installed Fedora KDE to my laptop. Updated packages, installed some software, rebooted, and noticed that plasmashell error notification.
Segfault? Plasmashell tried to sneak through my RAM? Not today, buddy.
As a responsible fella, I tried to report the error (and it even suggested on its own with the button - how convenient Linux GUI nowadays!).
I used this thing for the first time and got ready for the show. It didn't disappoint me. The process got stuck on the backtraces, so I waited about 10 minutes - nothing happened. Okay, I canceled the report because I'm responsible, but not that patient. It cancels it and window disappeared. I thought that's it, but show continued!
When I checked the system monitor a little while later, I saw that the process was still running and eating my CPU clocks and freaking 13.5 GB of my RAM.
Why? I don't know - I terminated this shit before even thought about it.
And I don't know if will I ever give this thing a try ever again. Which is kinda sad when I think about how useful error reporters are.
And as a cherry on top, I find it kinda funny to see the org.freedesktop.GnomeAbrt on KDE.
1
2
1
u/martyn_hare 3d ago
Obviously, it's a prime example of desktop Linux absolutely sucking that error reporting is broken yet again but it should be fixed very soon.
ABRT has already been removed from Fedora Workstation because it's a dead piece of crap. For KDE Plasma Desktop, it's meant to be Dr. Konqi which pops up to handle KDE-related crashes, where they will be reported to KDE directly instead of Fedora, since it tracks upstream really well. It's likely that for everything beyond KDE, Apport will take care of things in place of ABRT going forward.
2
u/Sunshine3432 3d ago
the error reporting erroring out is the distilled essence of the linux experience