From b5cbca36179b6f996eb72e0be6a889a6368550fa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Gr=C3=A4=C3=9Flin?= Date: Tue, 2 Feb 2016 10:19:46 +0100 Subject: [PATCH] Also consider the AcquiringLock state as a locked screen KSld goes to state AcquiringLock when starting the greeter process. During this state it expects the input to be grabbed. So from KWin perspective this means that the screen is locked and KWin should filter out input events. --- wayland_server.cpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/wayland_server.cpp b/wayland_server.cpp index 61e70c42af..091e4d7b04 100644 --- a/wayland_server.cpp +++ b/wayland_server.cpp @@ -509,7 +509,8 @@ quint16 WaylandServer::createClientId(ClientConnection *c) bool WaylandServer::isScreenLocked() const { - return ScreenLocker::KSldApp::self()->lockState() == ScreenLocker::KSldApp::Locked; + return ScreenLocker::KSldApp::self()->lockState() == ScreenLocker::KSldApp::Locked || + ScreenLocker::KSldApp::self()->lockState() == ScreenLocker::KSldApp::AcquiringLock; } }