https://bugs.kde.org/show_bug.cgi?id=416720
--- Comment #5 from lo...@kde.bt.alestan.publicvm.com --- (In reply to Zamundaaa from comment #1) > Sorry but this can't really be done. Managing output devices requires access > and control to global resources of the GPU. On the kms/drm level that's also > reflected by there only being one drm master per GPU - I'm surprised you > could make KWin run while a tty was active at all, it definitely doesn't > work with multiple compositors. > If you want multiple seats on a single GPU then you need a compositor that > manages that explicitly. In terms of running multiple compositors at once > that could be done by running them nested in a special compositor. AFAIK > compositors allowing such things don't really exist yet though I was under the impression that the login1 provider handled the kernel/drm level resource allocation, so handing the per-screen render plane to the compositor should be possible, but it might have poor security implications if the kernel-level (or hardware level) isolation aren't what they'd need to be. Given that a major goal of wayland is to resolve the security concerns that existed under X11, it's probably not worth pursuing further. That said, the poor behavior exhibited is not ideal, a clear error message that split-card-multiseat is unsupported by kwin shouldn't be too difficult to add, and would avoid the silent breakage / corrupted output. -- You are receiving this mail because: You are watching all bug changes.
