So far, I have to say that my #KDE #Plasma6 experience sucks.
The theme I was using doesn’t work. The icons all suck. EventCalendar, which was synced to my Google calendar is dead. Vivaldi looks like crap. The panel at the bottom of my screen is floating up probably 100 pixels, leaving useless space below it, I can’t find a way to sink it to the actual bottom of the screen. I had increased all my font sizes because my eyes are bad, they have all shrunk and changing the font sizes and the interface percentage doesn’t fix it.
So far, not a happy experience @kde
Also gotta keep in mind this is a major release. It’s allowed to break stuff, and the very first release is bound to have some bugs. We’re far into the Plasma 5 lifetime, a lot of the quirks have been ironed out.
It literally just came out, of course a lot of things haven’t been updated for it yet. Most people’s distros don’t even have it yet, addon authors don’t even know their addons are broken yet.
Well, yes. Lots of minor annoyance are popping up, most are being easily solved, so there will be a lot of minor updates over the next few weeks. 6.0.1 will be out in 6 days and a lot of the stuff annoying the early adopters will go away then.
How’s an average user supposed to know? I get updates almost every day and yeah there were a lot of packages last time but I didn’t realize it was a “major” release
What distro?
You really shouldn’t have 6.0 unless you’re on a rolling distro that’s very fast at updating packages. Even Arch doesn’t have 6.0 in the main repos yet, you only get it if you enable the testing repos. And that’s kind of what you sign up for with rolling distros, especially with testing repos enabled.
@Fleppensteijn @Max_P The change in the first component of the version number from 5 to 6 is what could have tipped you off. I mean, admittedly there’s no universal standard for software versioning that everyone follows, but the closest thing there is to a commonly adopted standard (https://semver.org/) says that when the first component of the version number changes, it’s a big deal and things might break. (Or, a relatively big deal, but just how big that is in practice depends on the package.) If you didn’t know to look out for that, now you do. 😀
Unless by “average user” you mean someone who relies on automatic updates and doesn’t look at what’s getting installed. Which is fine, but if you’re allowing automatic updates, you have to understand you’re giving up the ability to catch stuff like this before it happens. (This situation could certainly be improved, but generally that’s the state of things right now.)