Bug#914949: Issues with error message "Invalid MIT-MAGIC-COOKIE-1 key"

2018-11-28 Thread Vincent Lefevre 
Control: forwarded -1 https://gitlab.freedesktop.org/xorg/lib/libx11/issues/80

On 2018-11-29 01:10:06 +0100, Vincent Lefevre wrote:
> 2. As seen above, the error message does not end with a newline
> character. This breaks the parsing of the output (at least when
> both the standard output and the standard error are redirected
> to the same file).
> 
> This is confirmed with:
> 
> $ DISPLAY=:0 wine tversion.exe > /dev/null
> Invalid MIT-MAGIC-COOKIE-1 key%
> 
> under zsh, where the "%" output by zsh means that the newline character
> is missing.
> 
> I get the same issue with:
> 
> $ DISPLAY=:0 xterm
> Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/xterm: Xt error: Can't open display: :0
> 
> and with gxmessage (which doesn't use Xt), so that I assume that
> this comes from libX11. Reassigning this one to libx11-6.

Also reported upstream (hoping this is the right one).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Issues with error message "Invalid MIT-MAGIC-COOKIE-1 key"

2018-11-28 Thread Debian Bug Tracking System 
Processing control commands:

> forwarded -1 https://gitlab.freedesktop.org/xorg/lib/libx11/issues/80
Bug #914949 [libx11-6] libx11-6: error message "Invalid MIT-MAGIC-COOKIE-1 key" 
not followed by a newline character
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/xorg/lib/libx11/issues/80'.

-- 
914949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Issues with error message "Invalid MIT-MAGIC-COOKIE-1 key"

2018-11-28 Thread Vincent Lefevre 
Control: clone -1 -2
Control: retitle -1 libwine: spurious error message "Invalid MIT-MAGIC-COOKIE-1 
key" with invalid/old DISPLAY when X11 is not used
Control: reassign -2 libx11-6 2:1.6.7-1
Control: retitle -2 libx11-6: error message "Invalid MIT-MAGIC-COOKIE-1 key" 
not followed by a newline character

On 2018-11-28 18:19:46 +0100, Vincent Lefevre wrote:
> The output is actually present, but was filtered out later by
> the script due to an unexpected error message without a \n.
> 
> The tests/tversion.log starts with:
> 
> Invalid MIT-MAGIC-COOKIE-1 key[tversion] MPFR 4.1.0-dev
> [tversion] Compiler: GCC 7.3-win32 20180506
> 
> This message "Invalid MIT-MAGIC-COOKIE-1 key" is in tversion.log
> only, perhaps because the tversion test is executed first.

I can reproduce the issue with:

$ DISPLAY=:0 wine tversion.exe
Invalid MIT-MAGIC-COOKIE-1 key[tversion] MPFR 4.1.0-dev
[tversion] Compiler: GCC 7.3-win32 20180506
[...]

while there is no corresponding X server associated with :0. FYI,
this happens when the test is run in GNU screen and the X server
has shut down in the meantime.

Even though there is a workaround (unset DISPLAY), there are two
issues that should be fixed:

1. When X11 is not used like here, there is no reason to try to use
DISPLAY (or at least, error messages should be deferred). Note that
"env -u DISPLAY wine tversion.exe" doesn't output any error message.

2. As seen above, the error message does not end with a newline
character. This breaks the parsing of the output (at least when
both the standard output and the standard error are redirected
to the same file).

This is confirmed with:

$ DISPLAY=:0 wine tversion.exe > /dev/null
Invalid MIT-MAGIC-COOKIE-1 key%

under zsh, where the "%" output by zsh means that the newline character
is missing.

I get the same issue with:

$ DISPLAY=:0 xterm
Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/xterm: Xt error: Can't open display: :0

and with gxmessage (which doesn't use Xt), so that I assume that
this comes from libX11. Reassigning this one to libx11-6.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Issues with error message "Invalid MIT-MAGIC-COOKIE-1 key"

2018-11-28 Thread Debian Bug Tracking System 
Processing control commands:

> clone -1 -2
Bug #914822 [libwine] libwine: error message "Invalid MIT-MAGIC-COOKIE-1 key" 
without a \n
Bug 914822 cloned as bug 914949
> retitle -1 libwine: spurious error message "Invalid MIT-MAGIC-COOKIE-1 key" 
> with invalid/old DISPLAY when X11 is not used
Bug #914822 [libwine] libwine: error message "Invalid MIT-MAGIC-COOKIE-1 key" 
without a \n
Changed Bug title to 'libwine: spurious error message "Invalid 
MIT-MAGIC-COOKIE-1 key" with invalid/old DISPLAY when X11 is not used' from 
'libwine: error message "Invalid MIT-MAGIC-COOKIE-1 key" without a \n'.
> reassign -2 libx11-6 2:1.6.7-1
Bug #914949 [libwine] libwine: error message "Invalid MIT-MAGIC-COOKIE-1 key" 
without a \n
Bug reassigned from package 'libwine' to 'libx11-6'.
No longer marked as found in versions wine/3.0.3-2.
Ignoring request to alter fixed versions of bug #914949 to the same values 
previously set
Bug #914949 [libx11-6] libwine: error message "Invalid MIT-MAGIC-COOKIE-1 key" 
without a \n
Marked as found in versions libx11/2:1.6.7-1.
> retitle -2 libx11-6: error message "Invalid MIT-MAGIC-COOKIE-1 key" not 
> followed by a newline character
Bug #914949 [libx11-6] libwine: error message "Invalid MIT-MAGIC-COOKIE-1 key" 
without a \n
Changed Bug title to 'libx11-6: error message "Invalid MIT-MAGIC-COOKIE-1 key" 
not followed by a newline character' from 'libwine: error message "Invalid 
MIT-MAGIC-COOKIE-1 key" without a \n'.

-- 
914822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914822
914949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

mesa_18.2.6-1_source.changes ACCEPTED into unstable

2018-11-28 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 28 Nov 2018 22:58:22 +0200
Source: mesa
Binary: libxatracker2 libxatracker-dev libd3dadapter9-mesa 
libd3dadapter9-mesa-dev libgbm1 libgbm-dev libegl-mesa0 libegl1-mesa 
libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa libgles2-mesa-dev 
libglapi-mesa libglx-mesa0 libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-dev 
mesa-common-dev libosmesa6 libosmesa6-dev mesa-va-drivers mesa-vdpau-drivers 
mesa-vulkan-drivers mesa-opencl-icd
Architecture: source
Version: 18.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Description:
 libd3dadapter9-mesa - state-tracker for Direct3D9
 libd3dadapter9-mesa-dev - state-tracker for Direct3D9 -- development files
 libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library
 libegl1-mesa - transitional dummy package
 libegl1-mesa-dev - free implementation of the EGL API -- development files
 libgbm-dev - generic buffer management API -- development files
 libgbm1- generic buffer management API -- runtime
 libgl1-mesa-dev - free implementation of the OpenGL API -- GLX development 
files
 libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules
 libgl1-mesa-glx - transitional dummy package
 libglapi-mesa - free implementation of the GL API -- shared library
 libgles2-mesa - transitional dummy package
 libgles2-mesa-dev - free implementation of the OpenGL|ES 2.x API -- 
development files
 libglx-mesa0 - free implementation of the OpenGL API -- GLX vendor library
 libosmesa6 - Mesa Off-screen rendering extension
 libosmesa6-dev - Mesa Off-screen rendering extension -- development files
 libwayland-egl1-mesa - transitional dummy package
 libxatracker-dev - X acceleration library -- development files
 libxatracker2 - X acceleration library -- runtime
 mesa-common-dev - Developer documentation for Mesa
 mesa-opencl-icd - free implementation of the OpenCL API -- ICD runtime
 mesa-va-drivers - Mesa VA-API video acceleration drivers
 mesa-vdpau-drivers - Mesa VDPAU video acceleration drivers
 mesa-vulkan-drivers - Mesa Vulkan graphics drivers
Changes:
 mesa (18.2.6-1) unstable; urgency=medium
 .
   * New upstream release.
Checksums-Sha1:
 7557fd71986fb2ebd176ccf1c6200b0f26f37e54 5322 mesa_18.2.6-1.dsc
 8de0ea20dd458e0a12f1f190eae75c4fcab19279 19626522 mesa_18.2.6.orig.tar.gz
 a282aae472ca8b29a4540fa5c46e60e6e2ad6a09 879 mesa_18.2.6.orig.tar.gz.asc
 ea83831877682fbae4ab9fce8f36f2a7df119348 102411 mesa_18.2.6-1.diff.gz
 9081f96eb28361abd2f8114963ab770790bd2486 8881 mesa_18.2.6-1_source.buildinfo
Checksums-Sha256:
 ca7f82f1974c34fdd6c304b320d2579bdc2a4294bbae360ce829d69433f58c1d 5322 
mesa_18.2.6-1.dsc
 e0ea1236dbc6c412b02e1b5d7f838072525971a6630246fa82ae4466a6d8a587 19626522 
mesa_18.2.6.orig.tar.gz
 1e326647470c7fa28d3b4a1be759116b534ef3e6f9ced0339c9eb8fb2c21be91 879 
mesa_18.2.6.orig.tar.gz.asc
 25a91e92fd16c595c85872b2be0a3e220620dc72b0b6caf506e87eda087e06c0 102411 
mesa_18.2.6-1.diff.gz
 9977e72d52f870c9aa9722757c206e18532b9bb166feca743f0970a75fe3 8881 
mesa_18.2.6-1_source.buildinfo
Files:
 ec5b6bbbc99ca9cc6b30a152bb8d47e1 5322 graphics optional mesa_18.2.6-1.dsc
 b15d4e6ed4e9bea91efef787e69f3fd8 19626522 graphics optional 
mesa_18.2.6.orig.tar.gz
 cb4d71ab540ba78b091e3af6cc240ade 879 graphics optional 
mesa_18.2.6.orig.tar.gz.asc
 48b0734653a6917330de8222f0dc6cfe 102411 graphics optional mesa_18.2.6-1.diff.gz
 f63c8e54a3a4f19c925414373ac4a7cd 8881 graphics optional 
mesa_18.2.6-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlv/AYIACgkQy3AxZaiJ
hNw0ng/+M2yFOoVBojefEqibM44yYjgb2bz0QlzqwREfFANekrCDiGO6eUXVdxjq
SiXbZQEHHyZrWFTBNudQTQEjUyP1pxvjhSBKplmIU5oMS2OZQIEiGc8Nh1hsPLJ9
YDuRicEUVt0k+F+CvdTbujAzU+JMpnxTKiI9tC7lMlX3TszJaf+yXtL7TKhiKiZ/
b2pFrYlW3eGqz/cNu106YYOLwuZnOEcYmapBCFrstmIOIPohsQ54zaThGvkEd+Bi
F8lUIxAYYd/7IngtINlCLjq9E5wMQLKP+4ErFzsMgTTCrkK+8CIGAvN93fb9K+HK
aS7SR/tIJ7WRIWRQ3sIn3LR6oijTCD1x1QiCAv6FaSyCJbBsoVbkGRAC9q96J8vy
AeRhka2ASDbOQmN1bGZbOPJiSoZnn0/aID8ReCp3kS1MBZcOk/fK7GC09WWZToop
xuqkAAwEjNEhphiFpzNDcnvP6fvdJXvkWUXZhJm6EDIAK/2l7ewQAmAKLo1nBXvp
oMErpAnM/ehn3n/r/fMvUQA9TWpgtiH9quKv0AQCEWnXarJgHjaazlQLbFkDwK5c
XXDDMBuQc/8GsRgLAIhBdTwU8CS3sPbFvYUFBJftW9bPbxbGU/pakm+CNMaB1gAK
66kA68tyjBYXyAw5NI4qUAqG5FJyOTN/K5y/Ffd239pxR0KR+Bs=
=3DB/
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#894076: marked as done (Can't include GL and GLES headers simultaneously on non-64 bit architectures)

2018-11-28 Thread Debian Bug Tracking System 
Your message dated Wed, 28 Nov 2018 23:51:05 +0200
with message-id <20181128215105.GD7424@localhost>
and subject line This should be fixed in Mesa 18.2.5
has caused the Debian Bug report #894076,
regarding Can't include GL and GLES headers simultaneously on non-64 bit 
architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
894076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mesa
Version: 17.3.7-1
Severity: serious
Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=105328

Hi,

Currently it's impossible to include the GL and GLES headers
simultaneously on non-64 bit architectures, see e.g.
  
https://buildd.debian.org/status/fetch.php?pkg=gst-plugins-good1.0&arch=armel&ver=1.14.0-1&stamp=1521580828&raw=0

This causes

a) gst-plugins-base1.0 to only build with support for GL and not both
GL and GLES on the affected architectures,

b) causes gst-plugins-good1.0 to fail to build because Qt is including
the GLES headers, while GStreamer includes only the GL headers because
of the above

Currently gst-plugins-good1.0 fails to build on armel/armhf and can't
migrate to testing because of this bug. As a workaround I could force
gst-plugins-good to only build with GLES support on armel/armhf but
that's just that, a workaround.


This was reported upstream here
  https://bugs.freedesktop.org/show_bug.cgi?id=105328
and upstream agrees that this is a bug, and it seems easy enough to fix
by guarding the type definitions with the preprocessor to not redefine
them if they were already defined.


Thanks!

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 18.2.5-1

https://bugs.freedesktop.org/show_bug.cgi?id=105328#c9

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Processing of mesa_18.2.6-1_source.changes

2018-11-28 Thread Debian FTP Masters 
mesa_18.2.6-1_source.changes uploaded successfully to localhost
along with the files:
  mesa_18.2.6-1.dsc
  mesa_18.2.6.orig.tar.gz
  mesa_18.2.6.orig.tar.gz.asc
  mesa_18.2.6-1.diff.gz
  mesa_18.2.6-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

[Git][xorg-team/lib/mesa][upstream-unstable] 47 commits: cherry-ignore: add explicit 18.3 only nominations

2018-11-28 Thread Timo Aaltonen 
Timo Aaltonen pushed to branch upstream-unstable at X Strike Force / lib / mesa


Commits:
005fe7e0 by Juan A. Suarez Romero at 2018-11-21T09:12:24Z
cherry-ignore: add explicit 18.3 only nominations

Signed-off-by: Juan A. Suarez Romero 

- - - - -
ef6dabbb by Karol Herbst at 2018-11-21T09:12:24Z
nir/spirv: cast shift operand to u32

v2: fix for specialization constants as well

Reviewed-by: Jason Ekstrand 
Cc: mesa-sta...@lists.freedesktop.org
Signed-off-by: Karol Herbst 
(cherry picked from commit b4380cb070c0865f1fbfb3720056545665759bc3)

- - - - -
7c866498 by Jason Ekstrand at 2018-11-21T09:12:24Z
nir/lower_alu_to_scalar: Don't try to lower unpack_32_2x16

It messes up when trying to lower.

Cc: mesa-sta...@lists.freedesktop.org
Reviewed-by: Samuel Iglesias Gonsálvez 
(cherry picked from commit 4266932c0b301005dcc747fb6c2fef36a3af6ffe)

- - - - -
94161eed by Dylan Baker at 2018-11-21T09:12:24Z
meson: Don't set -Wall

meson does this for you with its warn levels, so we don't need to set
it ourselves.

Fixes: d1992255bb29054fa51763376d125183a9f602f3
   ("meson: Add build Intel "anv" vulkan driver")
Reviewed-by: Eric Engestrom 
(cherry picked from commit 9c2a95b29868f1388408b5eb9193fff39f942217)
[Juan A. Suarez: resolve trivial conflicts]
Signed-off-by: Juan A. Suarez Romero 

Conflicts:
meson.build

- - - - -
64f17d66 by Gert Wollny at 2018-11-21T09:12:24Z
mesa: Reference count shaders that are used by transform feedback objects

Transform feedback objects may hold a pointer to a shader program, and
at least in Gallium, this must be a valid pointer until
ctx->Driver.EndTransformFeedback in glEndTransformFeedback has been called
- which is conform with the spec that any program that is part of a
current rendering state should only be flagged for deletion by glDeleteProgram.
This was not handled properly for the transform feedback objects so that
a call sequence

  glUseProgram(x)
  glBeginTransformFreedback(...)
  glPauseTransformFeedback(...)
  glDeleteProgram(x)
  glEndTransformFeedback(...)

would result in a use after free bug. With this patch the transform
feedback object also updates the reference count to the used program
thereby keeping the program valid as long as the transform feedback
objects links to it.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108713
Fixes: 654587696b4234d09a6b471b70e9629cf2887c27
   mesa: add end_transform_feedback() helper

Signed-off-by: Gert Wollny 
Reviewed-by: Emil Velikov 
(cherry picked from commit caa964b422152788a95a1b248c884df8918a2bbd)

- - - - -
dad68bbd by Eric Engestrom at 2018-11-21T09:12:24Z
meson: only run vulkan's meson.build when building vulkan

Fixes: d1992255bb29054fa5176 "meson: Add build Intel "anv" 
vulkan driver"
Signed-off-by: Eric Engestrom 
Reviewed-by: Emil Velikov 
Reviewed-by: Dylan Baker 
(cherry picked from commit 3832db275efdb235b3b7b27c9b41e64d5507aa2c)

- - - - -
7a5bbce7 by Eric Engestrom at 2018-11-21T09:12:24Z
gbm: remove unnecessary meson include

`inc_wayland_drm` is only used if wayland is built, and it's already
added in that case a few lines below.

Fixes: a29869e8720b385d3692f "gbm: Don't traverse backwards for 
includes"
Signed-off-by: Eric Engestrom 
Reviewed-by: Emil Velikov 
Reviewed-by: Dylan Baker 
(cherry picked from commit 7df80de6e645ba8c20d97f5f2b1f6c12aa962e29)

- - - - -
21f97a6b by Eric Engestrom at 2018-11-21T09:12:24Z
meson: fix wayland-less builds

Those empty variables in the !wayland case are useless and running that
meson.build with them breaks the build:

  [287/850] Generating wayland-drm-client-protocol.h with a custom command.
  FAILED: src/egl/wayland/wayland-drm/wayland-drm-client-protocol.h
  client-header ../src/egl/wayland/wayland-drm/wayland-drm.xml 
src/egl/wayland/wayland-drm/wayland-drm-client-protocol.h
  /bin/sh: client-header: command not found
  ninja: build stopped: subcommand failed.

Fixes: d1992255bb29054fa5176 "meson: Add build Intel "anv" 
vulkan driver"
Signed-off-by: Eric Engestrom 
Reviewed-by: Emil Velikov 
Reviewed-by: Dylan Baker 
(cherry picked from commit 4fa2fb35245448f8b5d81fb5b37afec4f343f18a)
[Juan A. Suarez: resolve trivial conflicts]
Signed-off-by: Juan A. Suarez Romero 

Conflicts:
meson.build

- - - - -
83f1f651 by Eric Engestrom at 2018-11-21T09:12:24Z
egl: add missing glvnd entrypoint for EGL_ANDROID_blob_cache

Fixes dEQP-EGL.functional.get_proc_address.extension.egl_android_blob_cache
on builds with glvnd enabled.

Fixes: 6f5b57093b3462a54e9c7 "egl: add support for 
EGL_ANDROID_blob_cache"
Signed-off-by: E

[Git][xorg-team/lib/mesa] Pushed new tag mesa-18.2.6-1

2018-11-28 Thread Timo Aaltonen 
Timo Aaltonen pushed new tag mesa-18.2.6-1 at X Strike Force / lib / mesa

-- 
View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/tree/mesa-18.2.6-1
You're receiving this email because of your account on salsa.debian.org.

[Git][xorg-team/lib/mesa][debian-unstable] 50 commits: cherry-ignore: add explicit 18.3 only nominations

2018-11-28 Thread Timo Aaltonen 
Timo Aaltonen pushed to branch debian-unstable at X Strike Force / lib / mesa


Commits:
005fe7e0 by Juan A. Suarez Romero at 2018-11-21T09:12:24Z
cherry-ignore: add explicit 18.3 only nominations

Signed-off-by: Juan A. Suarez Romero 

- - - - -
ef6dabbb by Karol Herbst at 2018-11-21T09:12:24Z
nir/spirv: cast shift operand to u32

v2: fix for specialization constants as well

Reviewed-by: Jason Ekstrand 
Cc: mesa-sta...@lists.freedesktop.org
Signed-off-by: Karol Herbst 
(cherry picked from commit b4380cb070c0865f1fbfb3720056545665759bc3)

- - - - -
7c866498 by Jason Ekstrand at 2018-11-21T09:12:24Z
nir/lower_alu_to_scalar: Don't try to lower unpack_32_2x16

It messes up when trying to lower.

Cc: mesa-sta...@lists.freedesktop.org
Reviewed-by: Samuel Iglesias Gonsálvez 
(cherry picked from commit 4266932c0b301005dcc747fb6c2fef36a3af6ffe)

- - - - -
94161eed by Dylan Baker at 2018-11-21T09:12:24Z
meson: Don't set -Wall

meson does this for you with its warn levels, so we don't need to set
it ourselves.

Fixes: d1992255bb29054fa51763376d125183a9f602f3
   ("meson: Add build Intel "anv" vulkan driver")
Reviewed-by: Eric Engestrom 
(cherry picked from commit 9c2a95b29868f1388408b5eb9193fff39f942217)
[Juan A. Suarez: resolve trivial conflicts]
Signed-off-by: Juan A. Suarez Romero 

Conflicts:
meson.build

- - - - -
64f17d66 by Gert Wollny at 2018-11-21T09:12:24Z
mesa: Reference count shaders that are used by transform feedback objects

Transform feedback objects may hold a pointer to a shader program, and
at least in Gallium, this must be a valid pointer until
ctx->Driver.EndTransformFeedback in glEndTransformFeedback has been called
- which is conform with the spec that any program that is part of a
current rendering state should only be flagged for deletion by glDeleteProgram.
This was not handled properly for the transform feedback objects so that
a call sequence

  glUseProgram(x)
  glBeginTransformFreedback(...)
  glPauseTransformFeedback(...)
  glDeleteProgram(x)
  glEndTransformFeedback(...)

would result in a use after free bug. With this patch the transform
feedback object also updates the reference count to the used program
thereby keeping the program valid as long as the transform feedback
objects links to it.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108713
Fixes: 654587696b4234d09a6b471b70e9629cf2887c27
   mesa: add end_transform_feedback() helper

Signed-off-by: Gert Wollny 
Reviewed-by: Emil Velikov 
(cherry picked from commit caa964b422152788a95a1b248c884df8918a2bbd)

- - - - -
dad68bbd by Eric Engestrom at 2018-11-21T09:12:24Z
meson: only run vulkan's meson.build when building vulkan

Fixes: d1992255bb29054fa5176 "meson: Add build Intel "anv" 
vulkan driver"
Signed-off-by: Eric Engestrom 
Reviewed-by: Emil Velikov 
Reviewed-by: Dylan Baker 
(cherry picked from commit 3832db275efdb235b3b7b27c9b41e64d5507aa2c)

- - - - -
7a5bbce7 by Eric Engestrom at 2018-11-21T09:12:24Z
gbm: remove unnecessary meson include

`inc_wayland_drm` is only used if wayland is built, and it's already
added in that case a few lines below.

Fixes: a29869e8720b385d3692f "gbm: Don't traverse backwards for 
includes"
Signed-off-by: Eric Engestrom 
Reviewed-by: Emil Velikov 
Reviewed-by: Dylan Baker 
(cherry picked from commit 7df80de6e645ba8c20d97f5f2b1f6c12aa962e29)

- - - - -
21f97a6b by Eric Engestrom at 2018-11-21T09:12:24Z
meson: fix wayland-less builds

Those empty variables in the !wayland case are useless and running that
meson.build with them breaks the build:

  [287/850] Generating wayland-drm-client-protocol.h with a custom command.
  FAILED: src/egl/wayland/wayland-drm/wayland-drm-client-protocol.h
  client-header ../src/egl/wayland/wayland-drm/wayland-drm.xml 
src/egl/wayland/wayland-drm/wayland-drm-client-protocol.h
  /bin/sh: client-header: command not found
  ninja: build stopped: subcommand failed.

Fixes: d1992255bb29054fa5176 "meson: Add build Intel "anv" 
vulkan driver"
Signed-off-by: Eric Engestrom 
Reviewed-by: Emil Velikov 
Reviewed-by: Dylan Baker 
(cherry picked from commit 4fa2fb35245448f8b5d81fb5b37afec4f343f18a)
[Juan A. Suarez: resolve trivial conflicts]
Signed-off-by: Juan A. Suarez Romero 

Conflicts:
meson.build

- - - - -
83f1f651 by Eric Engestrom at 2018-11-21T09:12:24Z
egl: add missing glvnd entrypoint for EGL_ANDROID_blob_cache

Fixes dEQP-EGL.functional.get_proc_address.extension.egl_android_blob_cache
on builds with glvnd enabled.

Fixes: 6f5b57093b3462a54e9c7 "egl: add support for 
EGL_ANDROID_blob_cache"
Signed-off-by: Eri

Re: Bug#881333: Qt with GLES on arm64 maintainer's decision - Was:: Upcoming Qt switch to OpenGL ES on arm64

2018-11-28 Thread Lisandro Damián Nicanor Pérez Meyer 
El miércoles, 28 de noviembre de 2018 12:17:22 -03 Julien Cristau escribió:
> [dropping -devel, adding mesa and kde maintainers instead]

ACK.

> On 11/27/18 5:42 PM, Steve Langasek wrote:
> > On Mon, Nov 26, 2018 at 03:39:03PM -0800, Keith Packard wrote:
> >> Steve Langasek  writes:
> >>> Long ago I heard rumors of development work on mesa that would allow it
> >>> to
> >>> function as a proxy library, so that apps would link against libGL as
> >>> needed and the GL implementation would use a hardware-accelerated GLES
> >>> driver where possible, falling back to software GL where necessary.
> >> 
> >> This seems unlikely -- I believe GLES and GL have different semantics in
> >> a few places which makes implementing GL on GLES inefficient; mostly
> >> that GLES is missing stuff that GL applications often use, but I think
> >> there are places where GLES is just different, including in how GLSL
> >> works.
> > 
> > Perhaps that explains why no one ever actually succeeded in implementing
> > it, then?
> > 
> > Thanks for the context.
> > 
> >> I haven't tried, but I would expect that applications could use both GL
> >> and GLES APIs at the same time, even to the same window. If this does
> >> work with Mesa, then linking Qt against GLES wouldn't restrict
> >> applications using free drivers at least?
> > 
> > My recollection is that this becomes a practical problem of applications
> > that want to use both Qt and GL being unbuildable due to namespace
> > collisions at build time.
> 
> Do you know if there have been attempts at resolving those collisions
> upstream (either Qt or mesa / khronos)?
> 
> I seem to remember a couple of bug reports against mesa on the Debian
> side but am curious about any escalations.

The only thing I remember that sounds like this is:



"[arm] libgles2-mesa-dev and libglew-dev disagree over GLsizeiptr"

But maybe it was something else :-/

-- 
Ud. está viendo a la persona que ven nuestros clientes.
 Leyenda pegada en el espejo de una empresa.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

[Git][xorg-team/app/x11-apps][debian-unstable] 3 commits: Fix Vcs-Git control field

2018-11-28 Thread Julien Cristau 
Julien Cristau pushed to branch debian-unstable at X Strike Force / app / 
x11-apps


Commits:
94d97d7f by Julien Cristau at 2018-11-28T15:26:08Z
Fix Vcs-Git control field

- - - - -
e3069d63 by Andreas Henriksson at 2018-11-28T15:29:05Z
Pass MKTEMP=/bin/mktemp to configure

Fix reproducible build on merged-usr vs non-merged systems (x11perfcomp
embeds the path).

Closes: #914911

- - - - -
54836bac by Julien Cristau at 2018-11-28T15:30:44Z
Merge branch 'debian-unstable' into HEAD

- - - - -


3 changed files:

- debian/changelog
- debian/control
- debian/rules


Changes:

=
debian/changelog
=
@@ -1,7 +1,13 @@
 x11-apps (7.7+8) UNRELEASED; urgency=medium
 
+  [ Julien Cristau ]
   * Bump x11proto-core-dev build-dep to 7.0.25 per xwud's configure.ac.
 
+  [ Andreas Henriksson ]
+  * Pass MKTEMP=/bin/mktemp to configure to fix reproducible build
+on merged-usr vs non-merged systems (x11perfcomp embeds the path).
+(Closes: #914911)
+
  -- Julien Cristau   Sun, 18 Mar 2018 17:10:35 +0100
 
 x11-apps (7.7+7) unstable; urgency=medium


=
debian/control
=
@@ -52,7 +52,7 @@ Build-Depends:
 # xwd: libx11-dev, x11proto-core-dev
 # xwud: libx11-dev
 Standards-Version: 3.9.8
-Vcs-Git: https://salsa.debian.org/xorg-team/app/x11-apps
+Vcs-Git: https://salsa.debian.org/xorg-team/app/x11-apps.git
 Vcs-Browser: https://salsa.debian.org/xorg-team/app/x11-apps
 
 Package: x11-apps


=
debian/rules
=
@@ -30,7 +30,8 @@ $(STAMP_DIR)/configure-%:
dh_auto_configure -D$* -B$*-build -- \
--libdir=\$${prefix}/lib \
--disable-silent-rules \
-   MANCONF="/etc/manpath.config"
+   MANCONF="/etc/manpath.config" \
+   MKTEMP=/bin/mktemp
>$@
 
 override_dh_auto_build: $(BUILD_STAMPS)



View it on GitLab: 
https://salsa.debian.org/xorg-team/app/x11-apps/compare/58e86641118cef4277409e25f15866c269c1b1ca...54836bac7c71787c9f3810a89f54b4757aa257dd

-- 
View it on GitLab: 
https://salsa.debian.org/xorg-team/app/x11-apps/compare/58e86641118cef4277409e25f15866c269c1b1ca...54836bac7c71787c9f3810a89f54b4757aa257dd
You're receiving this email because of your account on salsa.debian.org.

Bug#914911: x11-apps: reproducible build (usrmerge): Embeds full path to mktemp found via PATH

2018-11-28 Thread Andreas Henriksson 
On Wed, Nov 28, 2018 at 03:44:01PM +0100, Andreas Henriksson wrote:
> Package: x11-apps
> Version: 7.7+7
> Severity: normal
> Tags: patch
[...]

Got some feedback. Improved patch attached.

Regards,
Andreas Henriksson
diff -Nru x11-apps-7.7+7/debian/changelog x11-apps-7.7+7+nmu1/debian/changelog
--- x11-apps-7.7+7/debian/changelog 2018-03-18 17:07:42.0 +0100
+++ x11-apps-7.7+7+nmu1/debian/changelog2018-11-28 16:05:57.0 
+0100
@@ -1,3 +1,11 @@
+x11-apps (7.7+7+nmu1) UNRELEASED; urgency=medium
+
+  * Pass MKTEMP=/bin/mktemp to configure to fix reproducible build
+on merged-usr vs non-merged systems (x11perfcomp embeds the path).
+(Closes: #914911)
+
+ -- Andreas Henriksson   Wed, 28 Nov 2018 16:05:57 +0100
+
 x11-apps (7.7+7) unstable; urgency=medium
 
   * Switch all xorg.freedesktop.org URLs in packaging to https.
diff -Nru x11-apps-7.7+7/debian/rules x11-apps-7.7+7+nmu1/debian/rules
--- x11-apps-7.7+7/debian/rules 2015-04-30 23:56:55.0 +0200
+++ x11-apps-7.7+7+nmu1/debian/rules2018-11-28 16:05:51.0 +0100
@@ -30,7 +30,8 @@
dh_auto_configure -D$* -B$*-build -- \
--libdir=\$${prefix}/lib \
--disable-silent-rules \
-   MANCONF="/etc/manpath.config"
+   MANCONF="/etc/manpath.config" \
+   MKTEMP=/bin/mktemp
>$@
 
 override_dh_auto_build: $(BUILD_STAMPS)

Re: Bug#881333: Qt with GLES on arm64 maintainer's decision - Was:: Upcoming Qt switch to OpenGL ES on arm64

2018-11-28 Thread Julien Cristau 
[dropping -devel, adding mesa and kde maintainers instead]

On 11/27/18 5:42 PM, Steve Langasek wrote:
> On Mon, Nov 26, 2018 at 03:39:03PM -0800, Keith Packard wrote:
>> Steve Langasek  writes:
> 
>>> Long ago I heard rumors of development work on mesa that would allow it to
>>> function as a proxy library, so that apps would link against libGL as needed
>>> and the GL implementation would use a hardware-accelerated GLES driver where
>>> possible, falling back to software GL where necessary.
> 
>> This seems unlikely -- I believe GLES and GL have different semantics in
>> a few places which makes implementing GL on GLES inefficient; mostly
>> that GLES is missing stuff that GL applications often use, but I think
>> there are places where GLES is just different, including in how GLSL
>> works.
> 
> Perhaps that explains why no one ever actually succeeded in implementing it,
> then?
> 
> Thanks for the context.
> 
>> I haven't tried, but I would expect that applications could use both GL
>> and GLES APIs at the same time, even to the same window. If this does
>> work with Mesa, then linking Qt against GLES wouldn't restrict
>> applications using free drivers at least?
> 
> My recollection is that this becomes a practical problem of applications
> that want to use both Qt and GL being unbuildable due to namespace
> collisions at build time.
> 
Do you know if there have been attempts at resolving those collisions
upstream (either Qt or mesa / khronos)?

I seem to remember a couple of bug reports against mesa on the Debian
side but am curious about any escalations.

Cheers,
Julien

Bug#914911: x11-apps: reproducible build (usrmerge): Embeds full path to mktemp found via PATH

2018-11-28 Thread Andreas Henriksson 
Package: x11-apps
Version: 7.7+7
Severity: normal
Tags: patch
User: m...@linux.it
Usertags: usrmerge

Dear Maintainer,

The reproducible build spotted a difference in your package when
built on a usrmerged system vs a non-merged system:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/x11-apps.html

It seems x11perfcomp contains the full path of 'mktemp' found via
AC_PROG_PATH during build.

Since PATH defaults to contain /usr/bin before /bin the found path will
be /usr/bin/mktemp on a usrmerged system, since both paths are
essentially the same thing there. This is however not desirable on
a non-merged system where it needs to be /bin/mktemp.

The attached patch fixes the problem by explicitly specifying
the default path via MKTEMP environment variable as documented
in AC_PROG_PATH documentation.

(This is likely a good idea either way, since otherwise hypothetical
problems could happen for users building on their system with
/usr/local/bin/... or ~/bin/)

Regards,
Andreas Henriksson


-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (400, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages x11-apps depends on:
ii  libc62.27-8
ii  libpng16-16  1.6.34-2
ii  libsm6   2:1.2.2-1+b3
ii  libx11-6 2:1.6.7-1
ii  libxaw7  2:1.0.13-1+b2
ii  libxcursor1  1:1.1.15-2
ii  libxext6 2:1.3.3-1+b2
ii  libxft2  2.3.2-2
ii  libxkbfile1  1:1.0.9-2
ii  libxmu6  2:1.1.2-2
ii  libxmuu1 2:1.1.2-2
ii  libxrender1  1:0.9.10-1
ii  libxt6   1:1.1.5-1
ii  man-db   2.8.4-3
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages x11-apps recommends:
pn  xbitmaps  

Versions of packages x11-apps suggests:
ii  mesa-utils  8.4.0-1
diff -Nru x11-apps-7.7+7/debian/changelog x11-apps-7.7+7+nmu1/debian/changelog
--- x11-apps-7.7+7/debian/changelog 2018-03-18 17:07:42.0 +0100
+++ x11-apps-7.7+7+nmu1/debian/changelog2018-11-28 15:22:57.0 
+0100
@@ -1,3 +1,10 @@
+x11-apps (7.7+7+nmu1) UNRELEASED; urgency=medium
+
+  * Explicitly set mktemp path via MKTEMP to make build reproducible
+on usrmerged vs non-merged systems. (Closes: #-1)
+
+ -- Andreas Henriksson   Wed, 28 Nov 2018 15:22:57 +0100
+
 x11-apps (7.7+7) unstable; urgency=medium
 
   * Switch all xorg.freedesktop.org URLs in packaging to https.
diff -Nru x11-apps-7.7+7/debian/rules x11-apps-7.7+7+nmu1/debian/rules
--- x11-apps-7.7+7/debian/rules 2015-04-30 23:56:55.0 +0200
+++ x11-apps-7.7+7+nmu1/debian/rules2018-11-28 15:22:50.0 +0100
@@ -16,6 +16,12 @@
 CONFIG_STAMPS = $(addprefix $(STAMP_DIR)/configure-, $(SUBDIRS))
 BUILD_STAMPS = $(addprefix $(STAMP_DIR)/build-,$(SUBDIRS))
 
+# Make build reprocudible by explicitly setting the path for mktemp.
+# AC_PATH_PROG will find /usr/bin/mktemp on usrmerged systems,
+# which is undesirable on non-merged systems. The full path
+# of mktemp is embedded in the built x11perfcomp script.
+export MKTEMP=/bin/mktemp
+
 %:
dh $@ --with quilt,autoreconf --parallel