This is used by the KCM

GIT_SILENT

This is the policy for e.g. dimming and turning off the screen,
i.e. "user can't see stuff anymore" which includes locking the screen.

"InterruptSession" is for suspend where the computer will not
continue its current tasks. The screen can still lock when I am
copying files or burning a CD.

BUG: 464119

There was no consesus for this in Plasma.
This reverts commit 78236123.

GIT_SILENT

GIT_SILENT

GIT_SILENT

I suspect this comes from the time before KF5Wayland joined Frameworks
with 5.22.0, but it serves no purpose nowadays.

KSignalHandler needs an instance of QCoreApplication because it uses
QSocketNotifier.

On mobile, we frequently spam our power buttons, of which each triggers a call from PowerDevil to ksldapp (in ksmserver) to lock the screen.

On the first call, it will start the greeter process. Subsequent calls send SIGUSR1 to the greeter process which is expected to be handled.

However, the greeter process doesn't start handling signals until after the lockscreen has loaded, which can take a few seconds.

During this period, any attempts to lock the screen (ex. pressing the power button) will cause the lockscreen to crash since SIGUSR1 isn't handled.

This MR ensures signal handling starts immediately at greeter start.

We need to apply the wallpaper anchors after the lockscreen theme is loaded, otherwise they won't be set properly and we end up with a black background.

This issue was triggered by !84

The reason why this wasn't noticed on Plasma Desktop, was that its lockscreen theme draws a FastBlur above the wallpaper in the background which will still correctly display the wallpaper item.

I had forgotten about that I used that as a workaround in Plasma Mobile for months... oops

resp was already checked although it was dereferenced before.