Bug 395813 - Searching for module and selecting it sometimes gives 'not a valid config module'
Summary: Searching for module and selecting it sometimes gives 'not a valid config mod...
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.13.1
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-24 12:16 UTC by Øystein Steffensen-Alværvik
Modified: 2020-11-11 04:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of error (37.80 KB, image/png)
2018-06-24 12:16 UTC, Øystein Steffensen-Alværvik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Øystein Steffensen-Alværvik 2018-06-24 12:16:00 UTC
Created attachment 113537 [details]
Screenshot of error

Searching for a systemsettings module from the search field and then selecting that module gives the error: 'The module [Window Management] is not a valid configuration module. The diagnosis is: The desktop file [settings-workspace-windowmanagement.desktop] does not specify a library'

How to reproduce:
1. Open Systemsettings
2. Search for 'management' or 'shutdown' (reproducable with both)
3. Select the result 'Window Management' or 'Startup and Shutdown'
Observe the error.

Reproducible always with these specific steps.
----
Output from terminal when reproducing:

QCoreApplication::arguments: Please instantiate the QApplication object first
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
KActivities: Database connection:  "kactivities_db_resources_140266896091456_readonly" 
    query_only:          QVariant(qlonglong, 1) 
    journal_mode:        QVariant(QString, "wal") 
    wal_autocheckpoint:  QVariant(qlonglong, 100) 
    synchronous:         QVariant(qlonglong, 0)
Nothing to load - the client id is empty
Nothing to load - the client id is empty
KActivitiesStats( 0x1a55ac0 ) ResultModelPrivate::onResultScoreUpdated  result added: "kcm:settings-workspace-session.desktop" score: 9 last: 1529841825 first: 1529841381
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "minimumHeight"
Comment 1 Patrick Silva 2018-08-05 21:31:19 UTC
Same bug on Arch Linux, plasma 5.13.4.
Comment 2 naraesk 2018-08-22 21:34:18 UTC
Can reproduce this on Arch Linux, plasma 5.13.4.

Noticed something strange:
When searching for "start" and clicking on the result "Starten und Beenden" it works fine all the time.

When searching for "starten" and clicking on the same entry "Starten und Beenden" it gives the error described above.

As far as I can tell the problem only exists for modules with a space in its name
Comment 3 Nate Graham 2020-10-12 22:04:33 UTC
That can happen with fed upgrades. Is this something you can reproduce with Plasma 5.19 or 5.20?
Comment 4 Bug Janitor Service 2020-10-27 04:33:32 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2020-11-11 04:34:01 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!