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

After updating to KDE 6.1 this morning on my Fedora 40 Desktop and rebooting, System Settings is displaying “Error loading QML file” for about 50% of the modules.

Most of the errors resemble this one, from the “Wallpaper” module:

qrc:/kcm/kcm_wallpaper/main.qml:104 Type NewStuff.Button unavailable

qrc:/qt/qml/org/kde/newstuff/Button.qml:90 Type NewStuff.Dialog unavailable

qrc:/qt/qml/org/kde/newstuff/Dialog.qml:104 Type NewStuff.DialogContent unavailable

qrc:/qt/qml/org/kde/newstuff/DialogContent.qml:55 Type NewStuff.Page unavailable

qrc:/qt/qml/org/kde/newstuff/Page.qml:133 Type Kirigami.InlineMessage unavailable

file:///usr/lib64/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_63*” as the former is neither the same as the latter nor a sub-class of it.

And this one from the “Sound” module:

qrc:/kcm/kcm_pulseaudio/main.qml:366 Type Kirigami.InlineMessage unavailable

file:///usr/lib64/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_63*” as the former is neither the same as the latter nor a sub-class of it.

Any help solving this would be greatly appreciated.

2 Likes

EXACT same thing happened to me.

Fedora 40.
KDE 6.1.

Keyboard Shortcuts menu:

Error loading QML file.

qrc:/kcm/kcm_keys/main.qml:66 Type Kirigami.InlineMessage unavailable
file:///usr/lib64/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_85*” as the former is neither the same as the latter nor a sub-class of it.

One more thing I’ll add. I was typing into the search bar in Settings to get to keyboard shortcuts. That’s where I got the QML error. I closed Settings and opened again, this time navigating to the section without using the search box. It worked just fine. Now, I’m trying to reproduce the issue using search, and I can’t figure out how I got the error. Maybe the error is transient or contextual, but I can’t reproduce it now. Weird.

Likely a caching issue see here:
https://bugs.kde.org/show_bug.cgi?id=488810

I managed to reproduce the error trying to do something completely different.

  1. Right click network icon in system tray area.
  2. Click “Configure Network Connections.”
  3. When System Settings opens, Click “Keyboard” → “Shortcuts”.

I get the error:

Error loading QML file.

qrc:/kcm/kcm_keys/main.qml:66 Type Kirigami.InlineMessage unavailable
file:///usr/lib64/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_82*” as the former is neither the same as the latter nor a sub-class of it.

Same thing here. Ultramarine Linux (Fedora 40).

edit: After a reboot most of the settings work again, but I can reproduce the error using the process from @TorrentRover above.

Have you tried removing or moving ~/.cache/systemsettings/qmlcache

Might need a reboot too.

2 Likes

@Duha, I tried renaming the qmlcache directory as you suggested. I couldn’t tell if it worked or not, because after a restart, 2 of 4 of my monitors were black or frozen (not moving, cursor wouldn’t paint). I tried messing with the monitors for a few minutes. Display settings in KDE were correct though, showing all 4 monitors in the correct place. So I renamed the qmlcache folder back and restarted. Now everything is normal again, but the QML error is still present obviously.

Just to be clear to everyone who may come across this later, this issue is easy to work around. Just close System Settings and open it again and go directly to where you were trying to go. It seems like this is an issue related to navigating from one section to the other. I don’t get the QML error unless I navigate around through different pages.

1 Like

Even if I logout, and via another tty delete my whole cache folder ~/.cache, all of these pages are broken:

Keyboard>Shortcuts
Sound
Display & Monitor
Bluetooth
Printers
Wifi & Internet> Firewall
Remote Desktop
Wallpaper
All Colors and Themes sub pages
Text & Fonts > Fonts
Notifications
Windows Management > Desktop Effects, Windows Rules, Scripts, Virtual Desktops
General Behavior
All Search sub pages
Application Permissions
User Feedback
Region & Language
Power Management
Autostart
Session> Desktop Session

1 Like

About this, there is a bug report: 488760 – systemsetting crashes after opening sound twice

Maybe more about this than that: After update to KF 6.3, many systemsettings pages of Plasma 6.0.90 show an error message

1 Like

Deleting the cache directory seemed to have temporarily fixed the problem (or maybe it was just coincidental), but it’s back again. This time deleting the cache directory did nothing. It seems to be very intermittent.

Oddly enough, some of the modules seem to start working again if I access System Settings by right clicking on the sound widget and selecting “Configure Audio Devices”. Accessing it through the Network Widget and navigating the keyboard shortcuts, as mentioned above, seems to reliably break almost all the modules.

1 Like

Worked for me. Arch BTW

file:///home/dell/.local/share/plasma/plasmoids/Plasma.Control.Hub/contents/ui/main.qml:647:53: NightColorInhibitor is not a type

Deleting .cache etc. or reboot did not help. (KDE neon 6.1)

Having the main Plasma app broken is really much worse than suffering from a crash of the whole desktop. :sob:

My issue got fixed when I unlinked .cache folder. Had it symlinked to another location. As to problem with Plasma Control hub plasmoid it’s up to dev to update it to support Plasma 6.1.

Deleting the contents of the ~/.cache/systemsettings/qmlcache directory, or everything in the ~/.cache/systemsettings directory really, doesn’t solve the issue. And neither does creating a new user who had no sessions before.

But the problem may still have been introduced by the recent update to Qt session management: After the Plasma update from 6.0.5 to 6.1, the default terminal emulator application was being auto-started at each login even though I didn’t have any .desktop file or startup script that was explicitly starting it, and I had to System Settings > System > Session > Desktop Session > select “Start with an empty session” for the “On login, launch apps that were open” setting in order to prevent it from being autostarted.

I updated to 6.1 via the terminal, restarted with qdbus org.kde.Shutdown /Shutdown logoutAndReboot, and the terminal emulator was being autostarted after that, since it was the only open window in the last session I guess.

1 Like

I am on Arch and everything is fine. Only issue I can see maybe it’s due to how I installed Plasma but no biggie, just don’t have the Shake to grow mouse pointer thingy in my settings. Maybe am missing a package. Don’t need it anyway so out of sight out of mind lol

I updated to Plasma 6.1 today. Everything is fine. I’m using KDE neon, shipped by the official makers of the KDE ecosystem. I used Fedora with Plasma Desktop and from my experience, here’s the take: Although Fedora ships updates with the latest updates, it is sometimes buggy and I have to deal with major bugs that I really have no time for. Hence I’ll use the more stable KDE neon OS.

I am also on a pretty clean KDE neon 6.1.
Did you try to change a global theme that you have to download (so not stock)? I was/am using the the apple sonoma global theme version 1.7.
It is working, but no Plasma Cotrol Hub and background image. When removed and reinstalled no luck. The only extra i am using is xrdp, which has his own problems from the 6.0 version I installed some time ago.

See the error i get in my first post.

There is nothing wrong here with System Settings, nor any other part of the system.

Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland