On Fri, 04 Jan 2013 13:47:12 +0200
Mika Boström wrote:
> On 01/04/13 13:30, Pekka Paalanen wrote:
> > That is strange. Why does Weston need any root access for you? Are you
> > perhaps running it via remote login, not local?
>
> That could be it. I'm doing everything I can over ssh. It's worked
On 01/04/13 13:30, Pekka Paalanen wrote:
> That is strange. Why does Weston need any root access for you? Are you
> perhaps running it via remote login, not local?
That could be it. I'm doing everything I can over ssh. It's worked
marvelously for intel+DRM case, so I naturally wanted the same ease
On Fri, 04 Jan 2013 10:32:43 +0200
Mika Boström wrote:
> On 01/03/13 20:46, Kristian Høgsberg wrote:
> >> Yep. Non-root user doesn't have permission to connect to Wayland socket.
> >
> > Weston will create the socket with permissions so that only the user
> > weston runs as can access it. This
On 01/03/13 20:46, Kristian Høgsberg wrote:
>> Yep. Non-root user doesn't have permission to connect to Wayland socket.
>
> Weston will create the socket with permissions so that only the user
> weston runs as can access it. This is deliberate and how the
> authentication works. As such, you can
On Thu, Jan 03, 2013 at 12:31:50PM +0200, Mika Boström wrote:
> I had a strange problem: after weston had started on RPi, I couldn't get
> any of the clients to run. I'm posting this in the hope that it will
> help someone else solve similar problems.
>
> Steps taken:
> 1. went with raspbian (from
I had a strange problem: after weston had started on RPi, I couldn't get
any of the clients to run. I'm posting this in the hope that it will
help someone else solve similar problems.
Steps taken:
1. went with raspbian (from official image)
2. rebuilt cairo packages to enable cairo-glesv2
3. follo
