... despite the numerous Plasma crashes lately.
... despite the numerous Plasma crashes lately.
Don't get me wrong, it looks absolutely BEAUTIFUL, but it crashes constantly, and it is a crapshoot on whether or not it will actually even BOOT within a virtual machine.
The KDE bug reporting process is completely broken.
You need an account on their system just to report a problem. I suspect that a large number of problems are never reported because the process of documenting them is just too difficult for most users. There is no automated crash reporting at all.
As far as I can tell the bugs that are reported go into a black hole and not addressed for years, if ever.
Or if you want to see a funny image, click this link: https://www.jwz.org/doc/cadt.html
If you're easily offended, google instead for "Cascade of Attention-Deficit Teenagers".
In February 2003, a bunch of the outstanding bugs I'd reported against various GNOME programs over the previous couple of years were all closed as follows:
"Because of the release of GNOME 2.0 and 2.2, and the lack of interest in maintainership of GNOME 1.4, the gnome-core product is being closed. If you feel your bug is still of relevance to GNOME 2, please reopen it and refile it against a more appropriate component. Thanks... This is, I think, the most common way for my bug reports to open source software projects to ever become closed. I report bugs; they go unread for a year, sometimes two; and then (surprise!) that module is rewritten from scratch -- and the new maintainer can't be bothered to check whether his new version has actually solved any of the known problems that existed in the previous version."
I'm so totally impressed at this Way New Development Paradigm. Let's call it the "Cascade of Attention-Deficit Teenagers" model, or "CADT" for short.
It hardly seems worth even having a bug system if the frequency of from-scratch rewrites always outstrips the pace of bug fixing. Why not be honest and resign yourself to the fact that version 0.8 is followed by version 0.8, which is then followed by version 0.8?
But that's what happens when there is no incentive for people to do the parts of programming that aren't fun. Fixing bugs isn't fun; going through the bug list isn't fun; but rewriting everything from scratch is fun (because "this time it will be done right", ha ha) and so that's what happens, over and over again.
© 2003 Jamie Zawinski <jwz@jwz.org>
Never heard of CADT before, but I have to admit that I've had experiences like this for sure (as the bug-reporter, not as the developer thank goodness).
I prefer to think of it as "aggressive refactoring" - which is not necessarily bad.
I think the process of software maintenance (in the context of KDE development) could be much improved if their reporting process had less friction and collected more relevant information so that the turnaround would be faster.
I think that there are interesting exceptions. For instance, the *BSDs are sometimes maddeningly conservative. But if you have last used FreeBSD 5.0 or OpenBSD 3.0, you are up and running on the latest versions in no time.
I hadn't looked at FreeBSD for years. Tried the latest version 6 months ago or so and configuration was pretty much the same as 10-15 years ago. There are new cool features (ZFS, bhyve), but it is all logical UNIX.
I think I want the complete opposite though - I want the latest Ubuntu core with a stable desktop.
I installed 17.04 over Win10 on my desktop a couple weeks ago—my first time making a serious go of Linux on the desktop since whenever Ubuntu wasted a ton of my time with their half-baked PulseAudio "upgrade", which was a long time ago at this point—and started with KDE (I know from some dabbling that I hate Unity), but was hitting application crashes and long busy-cursor issues at a rate of several an hour, across many K-series applications—including settings, and the file manager. I constantly had little "something crashed" icons in the tray (which, by the way, failed to be interactive when clicked, so they just sat there). After a few days of that I switched to Gnome (which on an SSD and a four-core desktop class processor with a pile of RAM is now tolerably responsive) and that all stopped.
Still no cure for awful tearing every time I scroll in FireFox :-/
What GPU are you using? There are various ways to fix this, depending on GPU/driver. I'd suggest looking in the Arch Wiki, even if you are using Ubuntu.
nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
I tried Kde Neon and was gobsmacked by the scale of change. With a few settings and a within a few minutes I was able to make it look and behave quite a bit like Unity. This was not the same KDE I remember.
It has improved dramatically and while the default is good you can feel the sheer flexibility of the underlying desktop. Kudos to the KDE team.
Unfortunately the Internet has a long memory and many will continue to repeat outdated information.