The bug-fixing continued this week with the aim of getting Plasma 6.0.3 into a great state. Already the big bugs you folks found have almost all been fixed, and this week a lot of time was spent on some X11 regressions and various crashes that our new automatic crash reporting system was able to find (thanks for submitting those! It really does help). A number of automated tests were also added, and finally some nice UI improvements to round things out. More exciting work is in progress too, but not quite ready to mention here!
Wayland is still unusable for me. Was happily running Wayland in 5.27 But have encountered nothing but issues in 6.0, main one being performing any sort of action with animations, scrolling, opening notifications etc causes the desktop frame rate to pummet, sometimes even hitting zero. All AMD build as well. I’ll keep checking back to see if it’s fixed but I’m too new to Linux to do any real sleuthing. X11 has been working fine in the meantime.
Use KJournald for a GUI Journald & kdebugsettings for controlling the program error log lvl. In KJournald, start with Emergency and work your way down to Warning. It’ll help you out greatly for identifying bugs.
Yes, spend a lot of time troubleshooting something that should already been stable
If you want it to be stable, you have to troubleshoot and send bug reports, and take advantage of Plasma 6 crash auto report system. Literally zero software is magically going to be completely bug free for every single possible hardware configuration. That’s just not how it works. It’s the entire reason why debug tools, debug symbols, auto report systems, bug trackers and so on exist for every single piece of software ever made.
I took the time to report bugs using a live ISO when plasma 6 was still in testing, and guess what? My system is more or less stable, even when plasma 6 first launched and everyone else were having a bunch of problems; which btw is to be expected and everyone else is aware of that except for apparently you. Only some minor harmless warnings persist now.
Bugs are fine, but we are not beta testers. It clearly wasn’t ready for the stable version
Actually, it was ready for the stable version.
The vast majority of the bugs reported by beta testers were fixed by the time the launch date rolled up. You just got unlucky where no beta testers had the same hardware configuration as you to test and discover bugs on.That’s the entire reason why the beta program is public, to get as many people as possible with a wide range of different hardware configurations to report as many bugs as possible in the early stages so they can fix them before launch.
There’s a huge difference in something used by 100s or 1000s of people. Once something is used significantly more it’ll result in bugs that nobody ever noticed before.
Further, the best way to keep things stable is regular timed releases. You seem to be advocating for releasing irregularly. Projects used to do that in the past. Regular releases result in way more stable software.
