https://bugs.kde.org/show_bug.cgi?id=489022
Bug ID: 489022
Summary: After opening the Mouse module, many other modules
fail to open with the message "Error loading QML file"
Classification: Applications
Product: systemsettings
Version: 6.1.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: 1293660...@qq.com
Target Milestone: ---
SUMMARY
After opening the Mouse module, many other modules fail to open with the
message "Error loading QML file". See below for more details.
STEPS TO REPRODUCE
1. Launch System Settings
2. Click on the Mouse & Touchpad module (and Mouse & Touchpad/Mouse will be
selected automatically)
3. Go back, and click on any module listed below (e.g. Sound)
OBSERVED RESULT
The following error message is shown (take Sound as an example):
qrc:/kcm/kcm_pulseaudio/main.qml:366 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_92*" as the former is neither the same as the
latter nor a sub-class of it.
EXPECTED RESULT
The corresponding module should open normally without error
SOFTWARE/OS VERSIONS
Linux: 6.9.5-arch1-1
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
ADDITIONAL INFORMATION
Affected modules:
- Keyboard/Shortcuts
- Sound
- Display & Monitor
- Bluetooth
- Thunderbolt
- WiFi & Internet/Firewall
- Wallpaper
- Color & Themes/*
- Text & Fonts/Fonts
- Notifications
- Window Management/Desktop Effects
- Window Management/Window Rules
- Window Management/KWin Scripts
- Window Management/Virtual Desktops
- General Behavior
- Search/*
- Application Permissions/Legacy X11 App Support
- User Feedback
- Region & Language
- Input Method
- Power Management
- Autostart
- Session/Desktop Session
The bug is only reproducible when you attempt to open an affected module
*after* opening the Mouse module. Otherwise, the bug will not be triggered.
Maybe related: bug 489018
--
You are receiving this mail because:
You are watching all bug changes.
