I used attached program to trigger it - it's modified fullscreen.c client
with 2 subsurfaces.
When I run it, press 'f' to make the main surface fullscreen and move
pointer over blue border, I get the crash.
On 16 July 2013 18:59, Rob Bradford wrote:
> On 16 July 2013 01:25, Mariusz Ceier wro
On 16 July 2013 01:25, Mariusz Ceier wrote:
>
> NULL pointer dereference happens when input->focus_widget == NULL
> and input->grab == NULL.
>
I worry this is working around the problem rather than addressing the
root cause. Why are we getting NULL for the focus_widget?
What steps did you take t
Calls into cairo-gles may change the current context, so it was only by
chance that sometimes we had the proper one as current and updated the
correct texture in surface_attach().
In order to fix this, calling display_acquire_window_surface() before
binding the texture for setup is necessary. Howe
weston-compositor and the weston-info client have also been updated to
pass on and print these values if present. The rate and delay defaults
originate from X.
---
clients/weston-info.c| 106 ---
src/compositor-wayland.c | 18 ++--
src/composito
In the process wl_keyboard's version has bben incremented. Given
clients get the wl_keyboard from wl_seat without a version, wl_seat's
version has also been incremented (wl_seat version 3 implies
wl_keyboard version 2).
---
protocol/wayland.xml | 17 +++--
1 file changed, 15 insertions
Make sure your using the 1.1 branch of Wayland and Weston, and the
stable branch of QtWayland.
By default when you compile QtWayland it will just provide you with a
QPA plugin which will allow you to run Qt applications inside a
Wayland compositor. QtWayland also contains apis to simplify creating
Hi,
I'm doing some r&d about Wayland and Weston for embedded systems.
So far I managed to cross compile Wayland, libxkbcommon and Weston for the
raspberry pi and it seems to be working well.
I'm now trying to deploy Qt5 libs to see what can be done... I cross
compiled Qt5 modules, but there are t
