Skip to content
Commit c63287ca authored by Devin Lin's avatar Devin Lin 🎨
Browse files

Fix crash condition where kscreenlocker_greet doesn't start handle signals in time 

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.
parent ee817536
Pipeline #285296 passed with stage
in 3 minutes and 17 seconds
Hide whitespace changes
Inline Side-by-side
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