Bug 479536

Summary: "Error loading QML file" in systemsettings
Product: [Applications] systemsettings Reporter: floriananton.schwarzl
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nicolas.fella
Priority: NOR Keywords: qt6
Version: 5.91.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Image showing the error in a specific section, happens in all

Description floriananton.schwarzl 2024-01-08 11:12:11 UTC
Created attachment 164749 [details]
Image showing the error in a specific section, happens in all

Seeing the following message in systemsettings instead of the usual options:

Error loading QML file.

qrc:/kcm/kcm_bluetooth/main.qml:19 Type 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_52*" as the former is neither the same as the latter nor a sub-class of it.




STEPS TO REPRODUCE
1. Install arch with kde plasma
2. Add the kde-unstable repo to /etc/pacman.conf
3. Update to Beta 2

KDE Plasma Version: Plasma 6.0 Beta 2 from kde-unstable
Qt Version: 6.7.0beta1-1

ADDITIONAL INFORMATION
Happened on two of my PCs, both running arch. They were set up seperatelly. Issue occured when updating from stable to unstable and then from beta 1 to beta 2. Issue doesn't occur in Beta 1.

Found a related issue (possibly same cause): https://forum.manjaro.org/t/error-loading-qml-file/67344
Comment 1 Nicolas Fella 2024-01-08 11:56:20 UTC

*** This bug has been marked as a duplicate of bug 478811 ***