System Settings app broken for me after update to KDE Plasma 6.1 (Fedora 40)

Help
22

Had the same issue on arch. I tried to install knewstuff an its QML dependencies (kirigami) (qt6-declarative) oddly it worked. I first removed qmlcache and qtpipelinecache-x86_64-little_endian-lp64 , but I’m sure it will be sorted out sooner or later. but its a temp fix if anything

so for the commands

I cant say this will fully fix it

paru -S knewstuff --overwrite "*" 
paru -S kirigami --overwrite "*" 
paru -S qt6-declarative --overwrite "*"

can prob do it all as one command but i was seeing witch one would fix the issue

Update after a reboot back to broken so ya i’ll leave it to the devs on this one. lol
I’d love to know more so i could help more but I’m new to qml stuff

1 Like
23

Been through a few forum posts looking for an answer. Running Bazzite Stable (based on Fedora 40 Kinoite) and kept getting the QML error on various setting modules. Eventually the settings app crashed, and when it opened again, everything was fixed…

24

Looks like there was a Kwin? update today,
just update
And reboot an looks like the problem is solved.

***Update*** yea its still broken, if you go into mouse an trackpad and then go into one of the affected setting the error is back only way to fix it is restart or log out an back in. So maybe avoid mouse tell its fixed.

25

After upgrading, it seems the problem is reproducible only after you start Plasma settings app for the first time after a fresh login, but when you close and reopen it, the problem is gone.

It seems like the app needs something initialized for the first time, it doesn’t find it (maybe lost after logout), but after second launch it succeeds.

26

If this can help, qt6-qtdeclarative(6.7.1-4) and breeze-icon-theme (6.3.0-2) are updated in the testing repo (40 packages): fedora-updates-testing.repo

Otherwise and until a fix is applied, this was the solution for the same issue with qt6.7 beta one (removes QML errors). Try tweaking home .config as follow:

~/.config/environment.d/envvars.conf
QML_DISABLE_DISK_CACHE=1

27

Thank you, man. I’ve also had this problem of the terminal auto-opening at the startup and it seems your workaround works fine

28

The bug has been moved to here so and it looks like things are looking up 487904 – Stuff using Kirigami InlineMessage and PlaceholderMessage fail to load with error `Cannot assign object of type \"Action\" to property of type \"Action_QMLTYPE_72*\" as the former is neither the same as the latter nor a sub-class of it" `

~Update 07/03/2024
Looks like the fix is on the way

30

I reported this two days ago without a single response. I see the problem under Firewall settings, the latest settings update did nothing to resolve the issue.

31

So uhm… as someone trying KDE for the first time for HDR support, is this likely to be fixed at some point? Been several weeks now & it’s been a broken mess from the very beginning with these constant “Error loading QML file.” messages even after several fresh installs.

32

On my laptops running Manjaro unstable and Arch, this problem was already fixed and I can’t reproduce it.

KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.0
Graphics Platform: Wayland
33

I haven’t been able to reproduce the error on any of my systems for the last week, so I think it’s been mostly fixed. It’s possible you still have some bad cached files floating around though. Make sure you have all your updates installed, reboot, and try clearing out the cached files mentioned further up in this thread.

34

Update the system today (with full clean reboot) and broke the settings with:

qrc:/kcm/kcm_keys/main.qml:66 Type Kirigami.InlineMessage unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/InlineMessage.qml:63 Type KT.InlineMessage unavailable
qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign object of type “TP.IconPropertiesGroup” to property of type “IconPropertiesGroup_QMLTYPE_79*” as the former is neither the same as the latter nor a sub-class of it.

I have reinstalled Kirigami and now seems to temp fix the problem so far.

1 Like
35

It works for me. Thanks!

36

That got it for me over here in Garuda. Thanks so much!!

1 Like
37

I installed OpenSUSE Tumbleweed and got the same message in KDE’s settings. Here’s the strange thing. After installation was completed, the default OpenSUSE wallpaper was being used, which is expected. After a reboot, KDE’s default wallpaper appeared (I didn’t change it) and the Settings error message went away. All Settings pages work as expected.