Don't start ksmserver with lockscreen integration on wayland

Summary:
Fixes regression from the startkde C++ re-write which made ksmserver
start the kscreenlocker in wayland session, resulting in the double
lockscreeens.

Test Plan: after applying patch I only get one lockscreen

Reviewers: apol

Reviewed By: apol

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D22021

startkde/startplasma-waylandsession.cpp

@@ -59,7 +59,7 @@ int main(int /*argc*/, char** /*argv*/)
     if (!startKDEInit())
         return 3;
 
-    if (!startKSMServer())
+    if (!startKSMServer(true))
         return 4;
 
     // Anything after here is logout

startkde/startplasma-x11.cpp

@@ -100,7 +100,7 @@ int main(int /*argc*/, char** /*argv*/)
     if (!startKDEInit())
         return 1;
 
-    if (!startKSMServer())
+    if (!startKSMServer(false))
         return 1;
 
     // Anything after here is logout

startkde/startplasma.cpp

@@ -338,7 +338,7 @@ bool startKDEInit()
     return true;
 }
 
-bool startKSMServer()
+bool startKSMServer(bool wayland)
 {
     // finally, give the session control to the session manager
     // see kdebase/ksmserver for the description of the rest of the startup sequence
@@ -355,9 +355,13 @@ bool startKSMServer()
 
 
     QStringList ksmserverOptions = { QStringLiteral(CMAKE_INSTALL_FULL_BINDIR "/ksmserver") };
+    if (wayland) {
+        ksmserverOptions << QStringLiteral("--no-lockscreen");
+    } else {
         if (desktopLockedAtStart) {
             ksmserverOptions << QStringLiteral("--lockscreen");
         }
+    }
     const auto exitCode = runSync(QStringLiteral("kwrapper5"), ksmserverOptions);
 
     if (exitCode == 255) {

startkde/startplasma.h

@@ -45,7 +45,7 @@ void setupGSLib();
 void setupX11();
 
 bool startKDEInit();
-bool startKSMServer();
+bool startKSMServer(bool wayland);
 
 void waitForKonqi();