[Wayland-bugs] [Bug 102307] Weston fails to run on seat1, because it needs a TTY. Only seat0 has TTYs

https://bugs.freedesktop.org/show_bug.cgi?id=102307 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Wayland-bugs] [Bug 102307] Weston fails to run on seat1, because it needs a TTY. Only seat0 has TTYs

https://bugs.freedesktop.org/show_bug.cgi?id=102307 --- Comment #5 from n3rdopolis --- I made https://lists.freedesktop.org/archives/wayland-devel/2017-August/034860.html It seems to work -- You are receiving this mail because: You are the assignee for the

[Wayland-bugs] [Bug 102307] Weston fails to run on seat1, because it needs a TTY. Only seat0 has TTYs

https://bugs.freedesktop.org/show_bug.cgi?id=102307 --- Comment #4 from n3rdopolis --- For the second question I could try to disable the checks... ...but I might have to do some grepping to find out how to do that... I am willing to test a temporary patch... --

[Wayland-bugs] [Bug 102307] Weston fails to run on seat1, because it needs a TTY. Only seat0 has TTYs

https://bugs.freedesktop.org/show_bug.cgi?id=102307 --- Comment #3 from Pekka Paalanen --- 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

[Wayland-bugs] [Bug 102307] Weston fails to run on seat1, because it needs a TTY. Only seat0 has TTYs

https://bugs.freedesktop.org/show_bug.cgi?id=102307 --- Comment #2 from n3rdopolis --- Hi. It is associated with the seat, sorry I wasn't clear, I discovered that I can set the logind seat to seat1 with systemd-run by specifying --setenv=XDG_SEAT=seat1 ... ...when

[Wayland-bugs] [Bug 102307] Weston fails to run on seat1, because it needs a TTY. Only seat0 has TTYs

https://bugs.freedesktop.org/show_bug.cgi?id=102307 Bug ID: 102307 Summary: Weston fails to run on seat1, because it needs a TTY. Only seat0 has TTYs Product: Wayland Version: unspecified Hardware: Other