On Sat, Oct 21, 2017 at 2:32 AM, Dima Ryazanov wrote:
> 1. Actually, Weston *should* set the right wayland socket automatically.
> They're not mapped to ttys - but Weston tries them until it finds an
> available one (at least, in my case). I see the following in the log:
>
> [23:52:27.077] libwayl
On Sat, Oct 21, 2017 at 12:28 AM, Matt Hoosier wrote:
>
> The trick here is to inform each compositor that it should be
> listening on a different Wayland socket name. For example, if you use
> Weston:
>
> $ weston --socket=wayland-1
>
> This will cause Weston to establish its listening socket
Hi
I have read the Wayland docs and skimmed through the API reference,
and I am trying to understand some concepts better. The questions
below are probably a bit naive, but I appreciate any
suggestions/explanations.
To illustrate my situation better, let me start with an actual
scenario I tried t
