Originally posted by mSparks
View Post
There is a absolutely simple mistake. Does weston forbid changing permissions on the socket after it created it. The answer is absolutely no.
Yes read the very thing you quoted completely.
> ** ONE-TIME SOLUTION **
>
> After weston has launched:
>
> % sudo chmod g+w /run/shm/wayland/wayland-0
>
> After weston has launched:
>
> % sudo chmod g+w /run/shm/wayland/wayland-0
Yes you can also do this as a normal user to let some other user access the wayland socket.
I very much doubt anything has changed since then, wayland is not just dead its full zombie.
Yes this is a myth about wayland caused by people not being able to read complete thing and notice that all the weston developer says is when weston creates the socket it will be created X way. The weston developer never says the permissions cannot be changed after the socket is created and then the person reporting the problem had included that as work around.
Comment