Created attachment 155763 [details] journalctl log of Plasma mobile session started from phog greeter SUMMARY Hi and thank you for developing plasma-mobile! Here using plasma-mobile 5.26.90 on up-to-date Mobian bookworm on OG PP. Plasma-mobile is not yet in Debian, but I've built it using [1]. In the last few weeks, I've been experiencing lot of issues with plasma-mobile, like session stuck ("loginctl unlock-session" white text on black screen) or not starting. Freeze deadline for Debian bookworm is on February,12th then a lot of new packages' versions are hitting the repo these days, including Qt-5.15.8, KDE Frameworks 5.102 and Plasma workspace 5.26.90. Could you please take a look at the attached journalctl log and help me spotting the issue? [1] https://salsa.debian.org/tiol/plasma-mobile/-/tree/debian/local SOFTWARE/OS VERSIONS Linux: 6.1.6-sunxi64 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8
Created attachment 155769 [details] journalctl log of Plasma mobile started as a system service after stopping phog
Created attachment 155830 [details] journalctl log of Plasma mobile started with startplasma-wayland
Created attachment 155932 [details] journalctl log of Plasma mobile starting as systemd service w/o phog/greetd/any-DM In this way, Plasma Mobile session is started, I can see lockscreen, but when I unlock the "[...] loginctl unlock-session 1 [...]" white writing on black background appears. Unlocking from serial console seems to bring session to a working state.
Ok, by starting plasma-mobile as a systemd service instead of from phog, it starts (even if the session crashes just out of kscreenlocker... filing a kscreenlocker bug for that). Then it's likely a phog issue. Closing