| Summary: | Plasma mobile session does not start kwin_wayland_drm: No suitable DRM devices have been found | ||
|---|---|---|---|
| Product: | [Plasma] plasma-mobile | Reporter: | Marco Mattiolo <marco.mattiolo> |
| Component: | general | Assignee: | Plasma Mobile Bugs <plasma-mobile-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
journalctl log of Plasma mobile session started from phog greeter
journalctl log of Plasma mobile started as a system service after stopping phog journalctl log of Plasma mobile started with startplasma-wayland journalctl log of Plasma mobile starting as systemd service w/o phog/greetd/any-DM |
||
|
Description
Marco Mattiolo
2023-01-29 14:31:34 UTC
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 |