On Sun, Oct 31, 2010 at 3:21 PM, Peter Clifton wrote:
> On Sun, 2010-10-31 at 10:36 +0100, Sedat Dilek wrote:
>> I made a 2nd wayland build:
>>
>> OK, there is definitely a problem with $DISPLAY,
>> if I use a different one (for example DISPLAY=:1.0), I get "failed to
>> create compositor".
>> If
On Sun, 2010-10-31 at 15:32 +0100, Sedat Dilek wrote:
> On Sun, Oct 31, 2010 at 3:21 PM, Peter Clifton wrote:
> > On Sun, 2010-10-31 at 10:36 +0100, Sedat Dilek wrote:
> >> I made a 2nd wayland build:
> >>
> >
> > In my case, it was because mesa was compiled without --disable-gallium
> >
> > That
On Sun, 2010-10-31 at 10:36 +0100, Sedat Dilek wrote:
> I made a 2nd wayland build:
>
> OK, there is definitely a problem with $DISPLAY,
> if I use a different one (for example DISPLAY=:1.0), I get "failed to
> create compositor".
> If I want to use DISPLAY=:0.0, the error-message is "failed to
>
Before I forget, I switched als Window-Manager from KDE4 to Fluxbox to
see if the WM has influence on Wayland.
Here is what I see in VT-1 from where I started X via startx command
(I always bootup into runlevel-3):
Setting default value
Failed to read: session.screen0.tabs.intitlebar
Setting defa
I made a 2nd wayland build:
OK, there is definitely a problem with $DISPLAY,
if I use a different one (for example DISPLAY=:1.0), I get "failed to
create compositor".
If I want to use DISPLAY=:0.0, the error-message is "failed to
initialize display" ending with a Segmentation fault.
Having a look
Just as an addendum:
# udevadm trigger --verbose --subsystem-match=drm --subsystem-match=input
/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:03/LNXVIDEO:00/input/input4
/sys/devices/LN
