New branch 'upstream-unstable' available with the following commits:
commit d45de283ce1f9edafc6f33632fc917513c620912
Author: Bryce Harrington <br...@osg.samsung.com>
Date: Tue Feb 16 12:37:43 2016 -0800
configure.ac: bump to version 1.10.0 for the official release
commit 9d24f23e4d6ae23f272d9a828523db504aaaf989
Author: Bryce Harrington <br...@osg.samsung.com>
Date: Thu Feb 11 15:23:33 2016 -0800
releasing.txt: Script now figures out release name on its own
commit 07d0d386daad6a4528b14521d86860e1f094a7ef
Author: Bryce Harrington <br...@bryceharrington.org>
Date: Tue Feb 9 13:36:00 2016 -0800
configure.ac: bump to version 1.9.93 for the RC1 release
commit 6c19b69fcc6921344fe8f552bbbbe26b70549a65
Author: Derek Foreman <der...@osg.samsung.com>
Date: Thu Dec 3 14:07:12 2015 -0600
compositor-drm: the cursor plane only supports ARGB
Keep XRGB apps out of the cursor plane, only ARGB is supported.
This prevents programs like weston-simple-shm from landing in the cursor
plane and being misrendered.
Signed-off-by: Derek Foreman <der...@osg.samsung.com>
Reviewed-by: Pekka Paalanen <pekka.paala...@collabora.co.uk>
commit b0427569fd4a9ef40a4bd59c412f5ab9b17b944d
Author: Derek Foreman <der...@osg.samsung.com>
Date: Fri Feb 5 15:55:20 2016 -0600
compositor-drm: update internal cursor plane location when disabling cursor
When the cursor plane is disabled the kernel can lose its location.
If we don't update our internal idea of where the plane is at that time,
the next time we set a cursor it can show up at 0,0.
This can show up when an application is put in the cursor plane, removed
from the plane, then put back at the same location. It might show up at
0,0 when it's reinstated.
We now use INT32_MIN as a location for disabled cursors so enabling the
plane will always cause an update.
Reviewed-by: Pekka Paalanen <pekka.paala...@collabora.co.uk>
Signed-off-by: Derek Foreman <der...@osg.samsung.com>
commit 345b4f5b119d20ace14a6cb4a96a8b1d91c05659
Author: Marek Chalupa <mchqwe...@gmail.com>
Date: Wed Feb 3 14:03:00 2016 +0100
compositor-x11: send pointer frame after axis event
clients that implement pointer interface of version 5
wait for the frame event, so without it the scrolling
does not work (GTK+ clients do not scroll now for example).
Xcb axis events are discrete, so it's fine to send
frame after every single axis event
Signed-off-by: Marek Chalupa <mchqwe...@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutte...@who-t.net>
commit 4e18448286ff27942ed3ad8fda568008c14eeff7
Author: Derek Foreman <der...@osg.samsung.com>
Date: Mon Feb 1 14:36:57 2016 -0600
xwm: Don't clear the selection if it has no text type available
weston maintains a copy of the most recently selected "thing" - it picks
the first available type when it copies, and saves that one only.
When an application quits weston will make the saved selection active.
When xwm sees the selection set it will check if any of the offered types
are text. If no text type is offered it will clear the selection.
weston then interprets this in the same way as an application exiting and
causing the selection to be unset, and we get caught in a live lock with
both weston and xwayland consuming as much cpu as they can.
The simple fix is to just remove the test for text presence.
Signed-off-by: Derek Foreman <der...@osg.samsung.com>
Reviewed-by: Carlos Garnacho <carl...@gnome.org>
commit 22b1f93432c775b6ed077c15a19e9e734a2806a5
Author: Bryce Harrington <br...@osg.samsung.com>
Date: Wed Sep 23 17:30:43 2015 -0700
shell: Check more thoroughly for undefined surface resource
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 wayland calls.
update v2:
* Fix some c/p errors for pointer names
* Drop null ptr check in add_popup_grab; probably redundant now
Signed-off-by: Bryce Harrington <br...@osg.samsung.com>
Reviewed-by: Daniel Stone <dani...@collabora.com>
commit 90c2789e8d83a5b090cf4b91a6770a93f08028a0
Author: Nobuhiko Tanibata <nobuhiko_tanib...@xddp.denso.co.jp>
Date: Sat Dec 26 23:52:51 2015 +0900
ivi-layout: apply opacity to weston_view correctly
update_opacity is only called when a ivi-surface is visible. But the
previous code also checks event masks redundantly. However if the event
happens when ivi-surface is invisible, opacity is not calculated. This
patch removes this redundant check to fix potential bug.
Signed-off-by: Nobuhiko Tanibata <nobuhiko_tanib...@xddp.denso.co.jp>
Reviewed-by: Pekka Paalanen <pekka.paala...@collabora.co.uk>
