https://bugs.kde.org/show_bug.cgi?id=421566
David Faure <fa...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Latest Commit| |https://invent.kde.org/fram
| |eworks/kcmutils/commit/0f44
| |2313d3357ef5d3cf1d341994466
| |0d49d146d
Resolution|--- |FIXED
--- Comment #10 from David Faure <fa...@kde.org> ---
Git commit 0f442313d3357ef5d3cf1d3419944660d49d146d by David Faure.
Committed on 20/05/2020 at 20:50.
Pushed by dfaure into branch '2020_05_fix_yast_crash'.
Fix crash when loading an external app KCM like yast
This re-instates the use of KService as a first-class citizen
in KCModuleInfo, apparently needed for non-plugins.
A unittest ensures that the very basic use of service() on such
a desktop file doesn't crash.
M +2 -1 CMakeLists.txt
A +7 -0 autotests/CMakeLists.txt
A +8 -0 autotests/YaST-systemsettings.desktop [TRAILING SPACE] **
A +42 -0 autotests/kplugininfotest.cpp [License: LGPL (v2/3+eV)]
M +53 -18 src/kcmoduleinfo.cpp
The files marked with ** at the end have a problem. either the file contains a
trailing space or the file contains a call to a potentially dangerous code.
Please read: http://community.kde.org/Sysadmin/CommitHooks#Email_notifications
Either fix the trailing space or review the dangerous code.
https://invent.kde.org/frameworks/kcmutils/commit/0f442313d3357ef5d3cf1d3419944660d49d146d
--
You are receiving this mail because:
You are watching all bug changes.
