Hopefully that update fixed the spectacle bug:
2 Likes
4 Likes
201 packages were updated. Most from unstable.
I can confirm settings app not working:
qrc:/kcm/kcm_kaccounts/main.qml:17 Type KCM.ScrollViewKCM unavailable
qrc:/qt/qml/org/kde/kcmutils/ScrollViewKCM.qml:25 Type KCM.AbstractKCM unavailable
qrc:/qt/qml/org/kde/kcmutils/AbstractKCM.qml:41 Type Kirigami.Page unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/Page.qml:237 Type Kirigami.PageRow unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:180 Type OverlayDrawer unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/OverlayDrawer.qml:22 Type KT.OverlayDrawer unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlayDrawer.qml:120 Cannot assign object of type "KTP.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_67*" as the former is neither the same as the latter nor a sub-class of it.
As far as I can see, there is no bug reported about this yet at bugs.kde.org.
META-1, META-2 etc still not working at my end.
I’ll see what else has improved or regressed.
Edit: yakuake systray icon is now adhering to the black/white colour scheme; hurray!
They have been working on the spectacle problem:
Reduced the memory usage of screen recording using KPipeWire. This won’t entirely fix the issue of screen recording taking up too much memory, but it makes a big difference already and should prevent outright resource exhaustion (Arjen Hiemstra, link 1 and link 2)
1 Like
It is a known issue, but it is caused by QT and was reported there.
PS: I’m dualbooting Garuda now (you posted the link to their forum thread above). They build against QT 6.6 and provide daily KDE snapshots. Different enough to provide some extra fun.
Thanks, I’ll have a look.
Sounds interesting. Have tried Garude a long time ago. Will have a look over there.
Switching from Plasma 5 to Plasma 6 when new Plasma is out is possible ? Just with yay or system update
When Plasma 6 is released running yay will indeed
upgrade your plasma 5 to plasma 6. Your won’t have to do anything special.
Read the thread- Ulf really knows his QT stuff, I believe.
Reading a thread like this makes me realize that there are dedicated, knowledgeable people involved in creating something that I use on a daily basis without actually really knowing that I am using it.
That’s interesting!
Does that mean their releases track the KDE git instead of Arch KDE unstable releases?
Does anyone have a weird issue where Dolphin doesn’t report disk usage with BTRFS file system? Noticeably, Ark complained about not enough space when I unzip a file, despite doing it just fine with CLI. I posted a similar post on KDE forum. Everything works just fine with Beta 1.
Didn’t notice anything unusual so far.
Yes. Garuda has their own repo building kde latest regularly.
Currently I’m hopping between the Arch and Garuda installations. Both of them had issues in the past, but usually one is working, making it easy to sit out packaging/QT/KDE issues in one or the other.
2 Likes
Once Plasma 6 is out in the wild, I will have a spare partition on this laptop, and may decide to install Garuda on that to have a play with it - looks nice.
I’m super happy that Garuda provides their own “KDE latest” snapshots at the moment. And overall they sprinkle mostly agreeable technical sugar on top of “base Arch”. But I not gonna lie: their choices go a little bit too far for my taste. So don’t take it as an overall “I recommend Garuda” from me.
Personally I still strongly prefer EOS (or CachyOS if EOS wouldn’t exist).
1 Like
Understood.
It’s more that you reminded me that Garuda exists, and from their site i gather they are doing interesting stuff.
Most likely the experience with Garuda will remind me why EOS rocks. 
1 Like
I’m experiencing that too on the beta 2 now. Did you file a bug report?
No, I haven’t got around to do it yet. I have to revert to Plasma 5 for now because Qt 6.7 beta is a bit buggy and messed everything up.
Thanks for the reply. I’m going to look into it and try to file.