<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Weston fails to run on seat1, because it needs a TTY. Only seat0 has TTYs" href="https://bugs.freedesktop.org/show_bug.cgi?id=102307#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Weston fails to run on seat1, because it needs a TTY. Only seat0 has TTYs" href="https://bugs.freedesktop.org/show_bug.cgi?id=102307">bug 102307</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>I wonder, perhaps ideally the choice of the KMS device(s) should dictate if a TTY is needed or not. If the KMS device is used for TTYs, then we need to tell the TTY to back off properly, but if it is not, then I suppose we should not care about the TTY. I suppose the seat assignments via udev should be good for that? Oh... the same goes for the input devices. And if there is no TTY, weston should disable the VT-switching key bindings. Maybe all that could also allow running Weston on kernels with CONFIG_VT=n. Or, does Weston just have superfluous TTY/VT checks when it's using logind, and otherwise everything would just work?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>