Fix ksysguard not starting on plasmoid click

Authored by maxrd2 on Sep 28 2017, 11:50 AM.

Description

Fix ksysguard not starting on plasmoid click

Summary:
Plasmoid now uses KRun::openService() to launch ksysguard instead of KRun::openUrl() and apps data source.

After plasmoid has been running for some time (several hours, maybe days), clicking it would produce error:
"file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:389: TypeError: Cannot read property 'entryPath' of undefined"
instead of launching ksysguard.

Ksysguard now starts without delay after click, since url doesn't have to be looked up.

Reviewers: Plasma, davidedmundson

Reviewed By: Plasma, davidedmundson

Subscribers: cfeck, Frameworks, davidedmundson, plasma-devel

Tags: Plasma, Frameworks

Differential Revision: https://phabricator.kde.org/D7648

Details

Committed
davidedmundsonSep 28 2017, 11:50 AM
Reviewer
Plasma
Differential Revision
D7648: Fix ksysguard not starting on plasmoid click
Parents
R114:058136890030: SVN_SILENT made messages (.desktop file) - always resolve ours
Branches
Unknown
Tags
Unknown