Re: [PATCH] shell: Check more thoroughly for undefined surface resource

2015-09-14 Thread Bryce Harrington
On Tue, Sep 15, 2015 at 08:31:56AM +0800, Jonas Ådahl wrote: > On Mon, Sep 14, 2015 at 01:15:47PM -0700, Bryce Harrington wrote: > > On Mon, Sep 14, 2015 at 12:31:10PM -0700, Bryce Harrington wrote: > > > The surface can have an undefined resource in certain situations (such > > > as with xwayland)

Re: [PATCH] shell: Check more thoroughly for undefined surface resource

2015-09-14 Thread Jonas Ådahl
On Mon, Sep 14, 2015 at 01:15:47PM -0700, Bryce Harrington wrote: > On Mon, Sep 14, 2015 at 12:31:10PM -0700, Bryce Harrington wrote: > > The surface can have an undefined resource in certain situations (such > > as with xwayland). So, since NULL is a valid state for this parameter, > > and since

XDC 2015: Updated Schedule, Social Event, Video release form

2015-09-14 Thread Tom Stellard
Hi, I just wanted to pass along a few XDC updates: - I have made some changes to the schedule, but it should still be considered tentative. I will let announce once it has been finalized. - There is an informal get together planned for Tuesday night if you are in town early. Please sign up on

Re: [PATCH] shell: Check more thoroughly for undefined surface resource

2015-09-14 Thread Bryce Harrington
On Mon, Sep 14, 2015 at 12:31:10PM -0700, Bryce Harrington wrote: > The surface can have an undefined resource in certain situations (such > as with xwayland). So, since NULL is a valid state for this parameter, > and since the wl_resource_*, etc. calls require their parameters to be > non-NULL, m

[PATCH] shell: Check more thoroughly for undefined surface resource

2015-09-14 Thread Bryce Harrington
The surface can have an undefined resource in certain situations (such as with xwayland). So, since NULL is a valid state for this parameter, and since the wl_resource_*, etc. calls require their parameters to be non-NULL, make a practice of always checking the surface resource before making wayla

Re: [PATCH weston] shell: Make sure we actually have a resource in end_busy_cursor

2015-09-14 Thread Bryce Harrington
On Fri, Sep 11, 2015 at 02:30:39PM -0500, Derek Foreman wrote: > It's actually possible to get here after the surface has been destroyed, > especially when running client apps under valgrind. > > That probably shouldn't be able to segfault the compositor. > > Signed-off-by: Derek Foreman Accord