That’s sad news. I hope they get things sorted ASAP.
As a CFU* I’m in a difficult place now.
I’ll get in contact with my CFU-buddy.
- Compulsive Frequent Updater
2 Likes
Impressive thread. Lots of people involved in trying to get this release tested and ready. As a simple end user I hardly have any idea about these “back office” processes.
1 Like
One of the spectacle bug reports[1] has been marked as resolved:
Git commit 66774b90e2f346d681f3d27a271ce5ad82b82bf7 by Arjen Hiemstra.
Committed on 18/12/2023 at 12:00. Pushed by ahiemstra into branch ‘master’.
encoding: Track the number of frames in flight If the encoder cannot keep up, we can run into cases where either the filter or encode queues are filling up with frames, causing memory usage to increase unconstrained. Unfortunately, FFMpeg does not have any way to set limits on its internal queues. So instead, we manually track frames enqueued and dequeued so that we can drop frames should the queues fill up too fast. Related: [bug 469005]
Advice is to not update just yet, but:
2 Likes
Back up and running using SDDM after latest updates.
1 Like
deployment is still not completed:
https://bbs.archlinux.org/viewtopic.php?pid=2138473#p2138473
2 Likes
Thank you for the heads up
Update seems OK package wise now.
Alas the QT 6.7 beta breaks a few things - prominently you can’t access many panels in the System Settings.
that would be because:
simply wait until arojas posts that deployment is complete …
What I mean is that these bugs are upstream and not caused by the deployment. So for those to be resolved we probably have to wait for a QT 6.7 beta 2 (or handpick patches when they arrive).
We will see. KDE and QT 6.7 being in beta for the coming months creates an unfortunate double-testing situation using kde-unstable.
Hmmm. I didn’t quite realize that this (Qt6.7 beta being released) is now interfering with the release for Plasma 6 and Qt6.6.1.
Will Plasma 6 be running on Qt6.7 when it (Plasma 6) is going to be released?
It requires QT 6.6 or higher. But we don’t know how Arch is planing the rollout. QT 6.7 is supposed to come out a few weeks after Plasma 6. Maybe they let the Plasma 6 release cook for a few weeks in kde-unstable - maybe getting a first point update - before shipping it together with QT 6.7.
Eventually Plasma 6 has to run on QT 6.7, so it is worth testing. It’s just unfortunate from a enduser testing experience that your Plasma 6 testing is affected by the QT bugs on kde-unstable right now.
Your sentiment is echoed over at arch:
Packaging a Qt beta in kde-unstable will lead to wrong bug reports on the KDE site and hinder beta testing for KDE.
I understand the reasoning behind trying to test Qt 6.7 while also testing Plasma 6, but in practice, it’s made it impossible to test Plasma 6 and I’ve reverted to Plasma 5 after being on 6 since the Alpha. The system settings modules being borked is definitely a problem, but I’m also seeing hangs in the window switcher and mouse events being offset by a certain amount in some applications. My assumption is that those are Qt, but who can tell.
It would seem to make a lot more sense to either stick on Qt 6.6 until Qt 6.7 stabilizes (at the very least until they fix whatever broke systemsettings) or maybe provide another set of Plasma packages that depends on Qt 6.7. Two betas at once is a lot of instability.
In the meantime I’m still desperately not updating my Plasma6-setup at the moment.
Imho the update is fine now - considering that it is beta software and a few bugs are to be expected. The only big issue I experience is the Settings app not working - but you can still start the individual configuration modules in the terminal if you really need them. 
I’m tempted.
Mostly working here but watching video in FF seems to run up the cpu cores to 95 - 100%.
Thanks for the heads up.
Will update tomorrow.
Great update here tonight, most menu items including logout and so working again.
2 Likes