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
What do you see if you run weston on tty3 (rather than sway), without
setting WAYLAND_SOCKET or --socket?
On Sat, Oct 21, 2017 at 12:02 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 i
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] libwayland: unable to lock lockfile
/run/user/1000/wayland-0.lock, mayb
Hi Deepak,
On Fri, Oct 20, 2017 at 11:50 AM, Deepak Jois wrote:
> 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.
>
> T
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
On 12 October 2017 at 18:19, Yong Bakos wrote:
> Hi Emil,
>
>> On Oct 12, 2017, at 5:39 AM, Emil Velikov wrote:
>>
>> From: Emil Velikov
>>
>> This makes the header self-contained, since the struct is considered
>> opaque from waylad-cursor POV.
>>
>> As we're here move the wl_shm fwd. declarati
