FS#58704 - [systemsettings] Error loading plugin "kcm_lookandfeel", missing options in "workspace theme"

Attached to Project: Arch Linux
Opened by Strangiato (Strangiato) - Wednesday, 23 May 2018, 13:05 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 12 June 2018, 20:19 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


options are missing when I switch sections available in system settings > workspace theme.
Bug reported in

comment 18 says that this bug seems a packaging issue.

Additional info:
* package version(s) systemsettings 5.12.5-1
* config and/or log files etc.

Steps to reproduce:
open system settings, click "Configure" button on top, select "icon view" and click "Ok" button
open "workspace theme", switch between the sections available on the left side
Watch my screencast please.

Output when I start system settings via terminal
QCoreApplication::arguments: Please instantiate the QApplication object first
org.kde.kcoreaddons: Error loading plugin "kcm_lookandfeel" "The shared library was not found."
Plugin search paths are ("/usr/lib/qt/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set

This task depends upon

Closed by  Antonio Rojas (arojas)
Tuesday, 12 June 2018, 20:19 GMT
Reason for closing:  Fixed
Additional comments about closing:  kdeclarative 5.47
Comment by Antonio Rojas (arojas) - Wednesday, 23 May 2018, 19:13 GMT
No, this is not a packaging issue. The original upstream report was, but it has now become a messy mixture of unrelated issues. The "Error loading plugin" message is harmless and has been there forever. The actual error here is
file:///usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml:198:26: Unable to assign [undefined] to bool
file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:41: Error: Cannot assign [undefined] to int

Please open a new report upstream with the detailed steps that you posted here.