[Pinephone/Plasma-mobile] kscreenlocker crashes after resume from suspend

Describe your issue

What's the expected behaviour?

The plasma lockscreen should appear after resuming from suspend state

What's the current behaviour?

When turning on the phone after the configured suspend timeout, at first the screen stays black.

After pressing the power button a second time, this screen appears

Pressing the power button while the error screen is displayed apparently restarts the plasma session (tty logout appears and shortly afterwards, the plasma login screen shows up again).

How to reproduce your issue?

Turn on the phone after entering suspend state

What device are you using?

Pine64-Pinephone

On what postmarketOS version did you encounter the issue?

• edge (master branch)

• v22.06

• v21.12 (supported until 2022-07-12)

• I confirm that the issue still is present after running sudo apk upgrade -a

On what environment did you encounter the issue?

Phone environments

• Phosh
• Plasma Mobile
• Sxmo (Wayland/Sway)

How did you get postmarketOS image?

• from https://images.postmarketos.org
• I built it using pmbootstrap
• It was preinstalled on my device

What's the build date of the image? (in yyyy-mm-dd format)

Additional information

• the full message in kscreenlocker (not that it would be useful with a touch interface) -> https://invent.kde.org/plasma/kscreenlocker/-/blob/master/abstractlocker.cpp#L61
• I'm not sure what the 2nd argument to the displayed loginctl command resolves to, it doesn't look like a number
• I don't remember this being an issue on v21.12 (but I'm not sure if I tested it either)
• there is nothing unusual in dmesg after the issue occurs, is there a special location where plasma/kde stores their logs? Or do I need to enable logging somewhere first?

added device-pine64-pinephone ui-plasma-mobile labels

Confirmed on edge. How to reproduce:

1. Unlock the phone
2. Lock the phone
3. Hit the power button 3 times
4. See the errors

By Raymond Hackley on 2022-10-15T18:21:41

mentioned in issue #1544 (closed)

By Raymond Hackley on 2022-10-15T18:29:23

upstream issue https://invent.kde.org/teams/plasma-mobile/issues/-/issues/156

By espidev on 2022-10-15T19:23:17

if this happens you can unlock over SSH using sudo loginctl unlock-sessions or loginctl list-sessions; sudo loginctl unlock session 1 (or whatever session number is)

By Alexey Min on 2022-10-16T02:04:21

Unfortunately this issue seems to persist in V22.12 Pinephone image (new install to emmc via the 20221225 'installer' image).

To reproduce:

• Disconnect ssh session (this seems to inhibit suspend)
• In Settings, set a timeout for 'suspend'
• Allow suspend to take place (check by trying to reconnect ssh session)
• Wake device with power button. (It seems to take several presses to get the screen to remain on)
• The error screen as shown at the start of this issue is displayed.

By reconnecting ssh session 'loginctl unlock-session 1' can be used to restore the Plasma UI, after about a 15-20 second wait for the shell to reload.

Effectively, this issue prevents the use of suspend to obtain better battery life for the device.

The upstream issue https://invent.kde.org/teams/plasma-mobile/issues/-/issues/156 seems to have been closed.

By Chris Billington on 2022-12-28T10:16:08

I haven't tested it but apparently the kscreenlocker crash issue was only fixed somewhat recently -> https://invent.kde.org/teams/plasma-mobile/issues/-/issues/187

Any chance this could get backported to stable? Otherwise we might need to wait for a v23.06 (don't know if its even available on edge yet, its a bit tedious to trace the plasma mobile component versions to the packages)

By Zapeth on 2022-12-28T10:19:13

This looks like the issue I am seeing. In testing I found that the kscreenlocker crash can happen when turning the screen on by pressing the power button, even through the phone wasn't in suspend.

As in the original issue when first pressing the power button the screen remains black- on pressing it again (maybe twice...?) the crash sometimes occurs.

While monitoring .local/state/tinydm.log and trying to reproduce the issue, I saw the following error logged 3-4 times when the screen is coming back on:

kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.ServiceUnknown" 
 "The name org.freedesktop.UDisks2 was not provided by any .service files"

So I installed udisks2, which silenced that error.

Now, having turned the screen off with the power button, the lock screen seems to reliably appear with a single press of the power button. Could there have been a race condition which goes away when there are no errors being logged about udisks2?

By Chris Billington on 2022-12-28T19:27:42

Usage since above message confirms the issue continues to occur, seems the updated kscreenlocker is required to fix. This would be a worthwhile candidate to backport to Stable/v22.12 because it's a very visible issue.

By Chris Billington on 2023-01-01T16:49:56

According to the kscreenlocker commit log the fixes for this issue are included with Plasma v5.26.5, which should be available in pmOS v22.12(sp1) and indeed I haven't been able to reproduce it after upgrading.

Occasionally it still takes a few seconds for the unlock screen screen to be displayed after pressing the suspend button (showing a black screen instead), but at least its better than crashing the session.

By Zapeth on 2023-03-04T07:04:45

closed