PINE64
Screen blocker is damaged ("loginctl unlock-session c1" problem) - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Manjaro on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=130)
+---- Thread: Screen blocker is damaged ("loginctl unlock-session c1" problem) (/showthread.php?tid=16890)



Screen blocker is damaged ("loginctl unlock-session c1" problem) - Gon - 06-24-2022

Hi all, hope you can help me with this issue which is repeating eventually on my plasma mobile pinephone.

Sometimes, when the system suspends, and I try to unblock it, appears a black screen that says:

"The screen blocker is damaged and it cannot be unblocked; change to a virtual terminal, start session on it and execute the next command:

loginctl unlock-session c1

close the virtual terminal session typing Ctrl+D and change to the session you where using (Ctrl+Alt+F2)"

Do you know how can I fix this? I have searched on several webs but no success.

Thanks a lot.


RE: Screen blocker is damaged ("loginctl unlock-session c1" problem) - bedtime - 08-16-2022

I'm not sure, but I have the same problem.

*** EDIT ***

It's very naive in its workings, but I made a script to at least deal with the problem for the moment:

unlock.sh:
Code:
#!/bin/sh

while :; do
  echo "Unlocking...:
  loginctl unlock-session c1
  sleep 2
done

Make the script executable:

Code:
chmod +x unlock.sh

Go into 'Settings' in the pulldown menu. Then, Autostart -> Add -> Add Login Script, and choose the script above.

I've only tested this for a few hours, but it's working so far.


RE: Screen blocker is damaged ("loginctl unlock-session c1" problem) - Firewave - 09-29-2022

This only happened when I did lock/unlock the phone and I reduced the occurrences by disabling auto-lock.

With the latest updates this now always happens and the phone will no longer show the UI and is completely unusable. "loginctl unlock-session c1" gets rid of the error screen but then the screen stays black. Restart sddm doesn't help either. Neither does a reboot.

I also that it takes a longer than usual (a few minutes) until it is connected with the network.