https://bugs.freedesktop.org/show_bug.cgi?id=88900
Pekka Paalanen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Pekka Paalanen <[email protected]> --- All the components here are way out of my expertise, but I think there are two different issues: - if weston fails in any way, it really shouldn't leave the VT (or kmscon) broken, especially when usind weston-launch where the VT handling is external to weston itself. (Might also be an issue with kmscon, not just weston or weston-launch). - weston fails to begin with I know little about systemd and logind, but is the shell inside kmscon in a real user session (in systemd/logind terms)? Does kmscon take DRM master? If yes, that means Weston cannot take it, and KMS calls will fail. Maybe that is the main issue. Unfortunately I have no idea how an app that wants to be a DRM master should run under something like kmscon. I'm adding David Herrmann to CC. Maybe he could explain how things are supposed to work between systemd, logind, kmscon, weston-launch, and weston. Btw. IIRC Sysrq-v is a thing that should forcefully restore fbcon, but I've no idea what it might do to kmscon. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
