Problems with the newest wayland git

[Bill Spitzak]

Pekka Paalanen wrote:
> On Thu, 15 Nov 2012 23:35:57 -0800
> Bill Spitzak <spitzak at gmail.com> wrote:
> 
>> This is not working very well for me. Most things point to EGL not 
>> working, but there are some strange problems.
> 
> What did you update first before you noticed it broke?

I updated and recompiled all of wayland, mesa, weston in that order 
before I tried it and found it not working. This was about 1 week after 
1.0 came out. Since then I have updated it several times, did a complete 
wipe of my build and rebuilt, and tried git update and make a few times 
atop this, and not much different has happened.

One of the git updates made mesa stop compiling until I located and 
compiled libdrm with new radeon driver code (even though I am not using 
the radeon driver, but I was unable to figure out any switches to mesa 
configure to stop it from looking for it). In any case this appeared to 
be succesful but it made no difference. That failure to build a version 
is really the only indication that anything changed in any versions.

> Are you sure you do not have any outdated weston components lying
> around? Like any of the backend or shell .so files? You do run 'make
> install' for weston before trying to run it?
> 
> If your update crosses some wayland-scanner changes, you'd better 'git
> clean -dxf' all wayland, weston, and mesa, to make sure the protocol
> files get regenerated. But sounds like you already tried that.

It is possible I never ran clean on wayland for the most recent ones. I 
certainly did for mesa (since that has fixed compiles before) and I also 
did it for weston yesterday. About 2 weeks ago I tried scrapping my 
entire checkout and rebuilding from scratch and deleted the install 
directory. This made no difference.

> Which 3D driver are you using?

This is running the x11-compositor on the nvidea x11 driver on a rather 
old nvidia graphics card. So far this has been the most successful setup 
for me, I used noveau for a while but have pretty much proven it has a 
bug that causes wayland to run really really slow (where it redraws 
after every event). This bug does not exist when using nvidea, and it 
certainly is not a compositor or window manager bug as it was consistent 
through a lot of versions of Ubuntu and a lot of different window 
managers including one I wrote myself that I know for a fact is not 
doing compositing!

I assume this means it is using mesa's software emulation of EGL. I have 
to tell you that the wayland compositor is surprisingly non-terrible in 
this mode!

I am perfectly willing to believe the EGL is not working because of this 
setup, but the results I am seeing where more than one wayland client 
crashes, and the fact that EGL worked before, leads me to think this is 
some other bug.