Members of the KDE Community are recommended to subscribe to the kde-community mailing list at https://mail.kde.org/mailman/listinfo/kde-community to allow them to participate in important discussions and receive other important announcements

Commit 552932c8 authored by Martin Flöser's avatar Martin Flöser

Disable kcrash in greeter in same way as in KWin

Summary:
When running KWin's lock screen test I saw:

KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kscreenlocker_greet path = /usr/lib/x86_64-linux-gnu/libexec pid = 20795
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --immediateLock --graceTime 5000 --ksldfd 85

This should not be as kcrash is supposed to be disabled. Comparing with
kwin showed a difference. This change brings in the same change as in
KWin.

Test Plan: KWin's lockscreen test no longer shows the kcrash debug

Reviewers: #plasma, #kwin

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D16943
parent b68a18b5
......@@ -85,6 +85,15 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
namespace ScreenLocker
{
// disable DrKonqi as the crash dialog blocks the restart of the locker
void disableDrKonqi()
{
KCrash::setDrKonqiEnabled(false);
}
// run immediately, before Q_CORE_STARTUP functions
// that would enable drkonqi
Q_CONSTRUCTOR_FUNCTION(disableDrKonqi)
class FocusOutEventFilter : public QAbstractNativeEventFilter
{
public:
......@@ -172,9 +181,6 @@ void UnlockApp::initialize()
m_resetRequestIgnoreTimer->setInterval(2000);
connect(m_resetRequestIgnoreTimer, &QTimer::timeout, this, &UnlockApp::resetRequestIgnore);
// disable DrKonqi as the crash dialog blocks the restart of the locker
KCrash::setDrKonqiEnabled(false);
KScreenSaverSettings::self()->load();
KPackage::Package package = KPackage::PackageLoader::self()->loadPackage(QStringLiteral("Plasma/LookAndFeel"));
KConfigGroup cg(KSharedConfig::openConfig(QStringLiteral("kdeglobals")), "KDE");
......
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