Well, I added only the kde-unstable this time (I may add testing in shortly). Things are a little freaky but mostly seem to work. Some of the settings don’t work…but I can live with that.
Konsole came up weird but I think I got it sorted out.
As I understand it, there is a workaround for this:
Here Konsole opens with all windows open, not just the terminal window. Is that what you mean?
I remember having read about this bug somewhere, will see if I can find more info.
Must dash now, though. Back later.
After last update widgets still not working at my end.
This has already been reported as a bug[1] during Beta 2.
Edit: as I understand it they have found the problem. I’m not much technically inclined, so I may well be misunderstanding what I’m reading here [2].
[1] https://bugs.kde.org/show_bug.cgi?id=478804
[2] https://bugreports.qt.io/browse/QTBUG-120191
Just to be clear: Individual widgets have to be updated and the user has to download and install the dedicated Plasma 6 version. 3rd party Plasma 5 widgets will not automagically start working again.
Ah, yes, you’re right of course, I forgot about this.
Thanks for the reminder.
In the meantime I figured out why I couldn’t compile a patched kwin version fixing the “no mouse cursor”-bug. Made a stupid mistake.
Arch RC1 is working again! 
Everything seems to be working in system settings now.
Afaik it shouldn’t. That was caused by a bug in the QT 6.7 beta and a fix for it wasn’t released yet. Did you apply a workaround you forgot about?
Just got the update now.
You’re right. Updated and System Settings is working again. 
Confirmed.
Nice!
Yes.
First one who files a bug report post a link so we can confirm.
I’m trying to find if a report has been submitted already, but I am unsure about the right keywords to look for.
1 Like
The cut off settings were already a problem in Beta 2. e.g. see https://bugs.kde.org/show_bug.cgi?id=478891
as far i understand it, that should be fixed in the next QT6.7 beta version.
3 Likes
Thank you @Metz, I would not have been able to find this.
I have not applied the work-around, though; but that is irrelevant I suppose?
As it is already supposed to have been solved, confirming it is not needed anymore?
Well if you can see the settings without the QML_DISABLE_DISK_CACHE workaround then its not longer necessary. That is good to know. I had not the time yet to test that.
And the cut-off bug should have been resolved by now as the QT 6.7 beta 2 should have been released yesterday already.
i guess we just have to wait. quite possible that we get it in the next hours or tomorrow.
Yes, confirmed: I did not apply the workaround; just updated with yay this afternoon and found out settings was working again only when @sammiev mentioned that they were working again.