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
parent
05813689
Please register or sign in to comment