It works fine. But it won’t always, as @Aragorn mentioned.
You should report any issues with the KDE team, then. Not Manjaro:
It works fine. But it won’t always, as @Aragorn mentioned.
You should report any issues with the KDE team, then. Not Manjaro:
5.26.4 should be out on the 2022-11-29 and 5.26.5 is scheduled for the 2023-01-03. After that all attention is on 5.27.x series. So lets see how fixable 5.26.x series is. For 5.24.8 I’ve no release date found yet …
It’s true that The Manjaro Team can only do so much, and that the rest is down to the devs that conceptualise and put together a working(stable?) desktop environment at the end of the day…
Well if you see a bug within 15 minutes in a fresh install you should report it. This most likely goes for KDE Neon or those who ship with vanilla look and feel: The 15-Minute Bug Initiative – Adventures in Linux and KDE
Scrolling throught their bugtracker similiar problems are already files multiple times, so i can only hope that this can be resolved. I mean until a week or two ago everything was fine.
Well - adding new regressions to “stable” versions seems to be partly a thing. Those happen sometimes also to the kernel development. So ya, we can only hope those won’t get backported to LTS versions …
Then the more visible bugs, admittedly… otherwise the others await to de discovered later on, so to speak.
Part of the truth IMO might be that the devs probably have real life situations, too, and skip through things to meet a theoretic deadline per see the release calender and such!..?
Latest Stable Updates (2022-12-06) now pulls in KDE Frameworks 5.100.0.
Anyone want to take the risk of updating, while sticking with KDE 5.24.7 LTS?
Is this the day we finally swallow the hard, bitter pill and accept our fate?
It would seem that way…
I use plasma 5.24.6. I updated everything except plasma and all seems to work fine.
It is possible that bugs will appear later but for now I don´t see any problem.
5.24.6?
Not 5.24.7?
Just applied today’s big update, still running 5.24.7. Seems OK…so far.
Yes 5.24.6.
You must have 9 lives…
After today’s update I see that you are indeed correct!
Based on Oldhabits experience, I tried it and he was indeed correct about Frameworks 100. This means that KDE is somewhat modular. But for how long?
I’ve done the update — with my fingers crossed — and I had no problems, except that Telegram Desktop had somehow disappeared from my Favorites in the Application Dashboard.
If you want to stay on Plasma 5.24 LTS, then you should upgrade to 5.24.7. Here’s how to do it.
I don’t think there’s any point in ignoring the plasma package group when you’re already on 5.26.2, because 5.26.3 is just around the corner. The advice to ignore those packages was for those on 5.24.6 who didn’t want to upgrade to 5.25.5. There is however — at least for now still — the option of switching to Plasma 5.24.7, which is the current LTS version. Assuming that the reader of this post is already on Plasma 5.26.x now, here’s how to do it…First, make a complete back…
Based on Oldhabits experience, I tried it and he was indeed correct about Frameworks 100. This means that KDE is somewhat modular.
That’s what I’ve been telling @philm as well.
There’s a reason why KDE chose to distribute the development of the Plasma experience over three different branches — i.e. Plasma Desktop, KDE Frameworks and KDE Gear (formerly KDE Applications) — which is that the three different branches would from there on be able to evolve independently and have their own release schedules without breaking compatibility.
Furthermore, the simultaneous existence of the 5.26.x mainline Plasma with the 5.24.x LTS Plasma suggests that KDE does indeed seek to maintain compatibility between the three projects, or at least, until the next major LTS branch appears, which is scheduled to be 5.27.x and which will be the last LTS branch before Plasma 6 is released, albeit that 5.27 LTS will then continue being maintained for quite a while still while 6.x is then the mainline.
When 4.x was released now mumble years ago, the very stable 3.5.x was suddenly dropped and people were forced to install the barely functional 4.x.
And to make matters worse, many distributions even deliberately broke existing 3.5.x installations in their update process because “it was unmaintained upstream anyway”, which caused a great number of KDE users to abandon KDE and switch to XFCE or GNOME, as well as that it also spawned a currently still maintained KDE 3.5 fork called Trinity Desktop Environment (TDE), and an also still maintained Plasma alternative called BE::Shell.
For all their chaotic decisions, I think KDE is still well enough aware of this past mistake to try and avoid that exodus from happening again.
KDE software is modular. Frameworks are used also in the mobile realm. Also other projects use KDE frameworks for their desktops. LxQt might come in mind. Deepin uses all sorts of frameworks also. JingPad, which failed due to a company not knowing how FOSS works, also used parts of KDE software.
All clear, so far. Let’s hope it stays that way…