This bug has been reported internally, but too late. Here is the fix for it : but be aware that it is modifying a file from the Lipstick, the compositor. If it’s done in a wrong way, the phone won’t start anymore…
--- a/usr/share/lipstick-jolla-home-qt5/lockscreen/LockScreen.qml
+++ b/usr/share/lipstick-jolla-home-qt5/lockscreen/LockScreen.qml
@@ -473,7 +473,7 @@ ApplicationWindow {
lockScreen.pinQueryPannable.deviceWasLocked = false
}
- if ((lockContainer.x > 0 || overshoot > 0) && !Lipstick.compositor.lockScreenLayer.lockScreenEvents
+ if ((lockContainer.x > 0 || absoluteProgress > 0) && !Lipstick.compositor.lockScreenLayer.lockScreenEventsEnabled
&& (Lipstick.compositor.notificationOverviewLayer.hasNotifications || Desktop.settings.left_peek_to_events)
&& Lipstick.compositor.systemInitComplete) {
lockItem.reset()
After doing the modification, you can run systemctl --user restart lipstick
from ssh. In case it goes wrong you can still go backward to the original file.