Commit 90839c80 authored by Bhushan Shah's avatar Bhushan Shah 📱

Set application name to org_kde_powerdevil

Summary:
Previously application component name without any KAboutData was
org_kde_powerdevil (executable name), although, 972eb26d commit
changed the component name to powerdevil, which had side-effects that
powerdevil would write shortcuts to powerdevil component and it would
conflict with old org_kde_powerdevil shortcuts, and ultimately none
would work.

In theory we can do migration of the shortcuts to powerdevil component
using kconf_update but that doesn't work, as kglobalaccel is already
started before powerdevil, resulting in kconf_update changes having no
effect, more on this in commit 4ae36ddd which introduces the
PowerDevilApp::migratePre512KeyboardShortcuts() function, while in
theory PowerDevilApp::migratePre516KeyboardShortcuts can be introduced,
we can simply avoid this hassle by re-assigning old component name.

BUG: 407721

Reviewers: davidedmundson, romangg

Reviewed By: davidedmundson

Subscribers: fvogt, arojas, plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D21303
parent 232a5045
......@@ -62,7 +62,7 @@ void PowerDevilApp::init()
{
KLocalizedString::setApplicationDomain("powerdevil");
KAboutData aboutData(QStringLiteral("powerdevil"), i18n("KDE Power Management System"), QStringLiteral(POWERDEVIL_VERSION_STRING),
KAboutData aboutData(QStringLiteral("org_kde_powerdevil"), i18n("KDE Power Management System"), QStringLiteral(POWERDEVIL_VERSION_STRING),
i18nc("@title", "PowerDevil, an advanced, modular and lightweight power management daemon"),
KAboutLicense::GPL,
i18nc("@info:credit", "(c) 2015-2019 Kai Uwe Broulik"));
......@@ -72,6 +72,7 @@ void PowerDevilApp::init()
aboutData.addAuthor(i18nc("@info:credit", "Dario Freddi"),
i18nc("@info:credit", "Previous maintainer"),
QStringLiteral("drf@kde.org"));
aboutData.setProductName("Powerdevil");
KAboutData::setApplicationData(aboutData);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment