I wonder if that driver is even supposed to support the EGL GBM platform.

To avoid GL and EGL problems, you could try with --use-pixman as an argument to weston.

(In reply to Pekka Paalanen from comment #1)
> I wonder if that driver is even supposed to support the EGL GBM platform.
> 
> To avoid GL and EGL problems, you could try with --use-pixman as an argument
> to weston.

I wouldn't think so, but then again I've never seen a version new enough that it supported EGL_EXT_client_extensions ...

This is almost certainly a bug or missing functionality inside the EGL driver: can you please provide the log file created from running weston --log=logfile.txt?

Created attachment 122222 [details]
Command bug multiple times but in different ways

Command bug multiple times but in different ways...
Number in "log-file*" are random.
(you can find the "log-file*" in other attachment)

That attachment is definitely not text/plain. Could you fix the mime type, please?

Created attachment 122224 [details]
PC SPEC

PC SPEC

Created attachment 122226 [details]
log-file1.txt

122222: Command bug multiple times but in different ways
log-file1.txt

Created attachment 122227 [details]
log-file2.txt

122222: Command bug multiple times but in different ways
log-file2.txt

Created attachment 122228 [details]
log-file05.txt

122222: Command bug multiple times but in different ways
log-file05.txt

Created attachment 122229 [details]
log-file33.txt

122222: Command bug multiple times but in different ways
log-file33.txt

I've found weston call eglSwapBuffers and crash in kms_swrast_dri.so on GMA500

Thread 2 "llvmpipe-0" received signal SIGBUS, Bus error.
[Switching to Thread 1379.1385]
0xb755e633 in ?? ()
(gdb) up  
#1  0xb6e2960b in lp_rast_shade_tile (task=0x80a9ab4, arg=...) at lp_rast.c:352

BEGIN_JIT_CALL(state, task);
         variant->jit_function[RAST_WHOLE]( &state->jit_context,
                                            tile_x + x, tile_y + y,
                                            inputs->frontfacing,
                                            GET_A0(inputs),
                                            GET_DADX(inputs),
                                            GET_DADY(inputs),
                                            color,
                                            depth,
                                            0xffff,
                                            &task->thread_data,
                                            stride,
                                            depth_stride);
so maybe this is bug in mesa

(In reply to comicfans44 from comment #10)
> I've found weston call eglSwapBuffers and crash in kms_swrast_dri.so on
> GMA500
...
> so maybe this is bug in mesa

Quite probably.

By the way, the only way how gma500 is involved here is that you don't have (proprietary) OpenGL drivers for it. Instead you have Mesa, which picks a software renderer, because it's all it has.

"GL renderer: Gallium 0.4 on llvmpipe" and kms_swrast_dri.so refer to software renderers in Mesa.

If you are stuck with software rendering anyway, you might as well forget OpenGL, because Weston's Pixman renderer should outperform software OpenGL any day, I believe. That's why I propose to just have --use-pixman for Weston. You can still run software-rendered GL apps with Mesa as your OpenGL implementation.

But if you really want to have kms_swrast_dri.so working, that's between you and Mesa, I think.

If --use-pixman works, there is nothing to fix in Weston.

(In reply to Pekka Paalanen from comment #11)
> (In reply to comicfans44 from comment #10)
> > I've found weston call eglSwapBuffers and crash in kms_swrast_dri.so on
> > GMA500
> ...
> > so maybe this is bug in mesa
> 
> If you are stuck with software rendering anyway, you might as well forget
> OpenGL, because Weston's Pixman renderer should outperform software OpenGL
> any day, I believe. That's why I propose to just have --use-pixman for
> Weston. You can still run software-rendered GL apps with Mesa as your OpenGL
> implementation.
> 
I haven't found --use-pixman option, did you mean --with-cairo=image ?

--use-pixman is an option to pass when running Weston, not at the configure stage.

Ha, I see we have forgotten to document --use-pixman in 'man weston-drm', but at least 'weston --help' prints it.

Created attachment 122329 [details]
--use-pixman make serverx error

With --use-pixman parameter I can't start x11 application. Solution?

It seems something has gone wrong with Xwayland; what that is I can't possibly guess from a picture of the screen. But that is something which works with --use-pixman and in general (I tested), so try looking at your logs, e.g. for failing to find the Xwayland binary, or not having the xwayland.so module loaded for Weston.

Created attachment 122374 [details]
Xwayland error log

(In reply to Pietro Sam from comment #17)
> Created attachment 122374 [details]
> Xwayland error log

You have not installed Xwayland yet.

I'd be more worried about the "queueing pageflip failed" messages, though. Maybe the poulsbo driver in the kernel is... lacking.

Anyway, nothing we can do for you here about the GMA500.