Re: [PATCH wayland] Require WAYLAND_DISPLAY to be set instead of using wayland-0 as the default

2015-08-14 Thread Dima Ryazanov
So, it seems like pretty much everyone agrees with this change. Could we actually get it in for the 1.9 release? On Thu, Aug 13, 2015 at 4:47 AM, Ryo Munakata ryomnk...@gmail.com wrote: On Wed, 12 Aug 2015 19:34:31 -0700 Dima Ryazanov d...@gmail.com wrote: Hi Dima. Reviewed-by: Ryo

Re: [PATCH wayland] Require WAYLAND_DISPLAY to be set instead of using wayland-0 as the default

2015-08-14 Thread Pekka Paalanen
On Wed, 12 Aug 2015 19:34:31 -0700 Dima Ryazanov d...@gmail.com wrote: Although defaulting to wayland-0 seems convenient, it has an undesirable side effect: clients may unintentionally connect to the wrong compositor. Generally, it's safer to fail instead. Here's a real example: In Fedora

Re: [PATCH wayland] RFC: Require WAYLAND_DISPLAY to be set instead of using wayland-0 as the default

2015-08-14 Thread Pekka Paalanen
On Thu, 13 Aug 2015 13:12:42 +1000 Peter Hutterer peter.hutte...@who-t.net wrote: On Wed, Aug 12, 2015 at 02:41:08PM +0300, Pekka Paalanen wrote: On Mon, 25 May 2015 01:12:15 -0700 Dima Ryazanov d...@gmail.com wrote: Although defaulting to wayland-0 seems convenient, it has an

Re: [PATCH wayland] Require WAYLAND_DISPLAY to be set instead of using wayland-0 as the default

2015-08-14 Thread Dima Ryazanov
Oh, you're right, I didn't realize that's what that code was doing. Thanks! On Fri, Aug 14, 2015 at 12:20 AM, Pekka Paalanen ppaala...@gmail.com wrote: On Wed, 12 Aug 2015 19:34:31 -0700 Dima Ryazanov d...@gmail.com wrote: Although defaulting to wayland-0 seems convenient, it has an

Re: [PATCH wayland] RFC: Require WAYLAND_DISPLAY to be set instead of using wayland-0 as the default

2015-08-14 Thread Ray Strode
Hi, thanks, and sorry I didn't see your reply before I pushed. :-D So this commit totally broke gtk+. Thread 1 (Thread 0x7f3813651980 (LWP 537)): #0 g_logv (log_domain=0x7f38128b01ce Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=optimized out) at ../../glib/gmessages.c:1078

[PATCH weston 1/2] Fix build breakage when using older gbm lacking dmabuf import

2015-08-14 Thread Bryce Harrington
The buildbots discovered this issue on Ubuntu 14.04, which carries libgbm 10.1.3-0ubuntu0.4. The dmabuf changes need gbm 10.2, so it fails during build like this: src/compositor-drm.c: In function ‘drm_output_prepare_overlay_view’: src/compositor-drm.c:984:10: error: variable ‘gbm_dmabuf’

[PATCH weston 2/2] Fix armhf configure breakage due to missing libdrm_intel package

2015-08-14 Thread Bryce Harrington
The buildbots discovered that recent changes break on Ubuntu 15.04's armhf images: configure:16137: checking for SIMPLE_DMABUF_CLIENT configure:16144: $PKG_CONFIG --exists --print-errors wayland-client libdrm libdrm_intel Package libdrm_intel was not found in the pkg-config search path.

Re: [PATCH] ivi-shell: bugfix, list of surfaces on a layer are cumulated when set render order is called several time in one commitchanges.

2015-08-14 Thread Pekka Paalanen
On Wed, 5 Aug 2015 16:00:57 +0900 Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp wrote: The final list of surfaces of set render order shall be applied. So link of surfaces and list of surfaces in a layer shall be initialized. And then the order of surfaces shall be restructured.

Re: [PATCH weston v2 0/8] Generic Wayland dmabuf protocol

2015-08-14 Thread Pekka Paalanen
On Wed, 1 Jul 2015 17:56:12 +0300 Pekka Paalanen ppaala...@gmail.com wrote: From: Pekka Paalanen pekka.paala...@collabora.co.uk Hi all, here is the v2 iteration of the Wayland protocol extension for generic sharing of dmabufs between clients and the compositor. The RFCv1 can be found