[Desktop-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

[Yogish Kulkarni]

When it is expected libegl-mesa0 to move from bionic-proposed to bionic-
updates ? thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1776499

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

[Yogish Kulkarni]

Before using libegl-mesa0 from bionic-proposed:
$ apt-cache policy libegl-mesa0
libegl-mesa0:
  Installed: 18.0.5-0ubuntu0~18.04.1
  Candidate: 18.0.5-0ubuntu0~18.04.1
  Version table:
 *** 18.0.5-0ubuntu0~18.04.1 100
100 /var/lib/dpkg/status
$ cat main.c 
main()
{
   eglGetProcAddress("egl148546488546404");
}
$ gcc main.c -lEGL
$ ./a.out 
Segmentation fault (core dumped)

After upgrading libegl-mesa0 to bionic-proposed:
$ apt-cache policy libegl-mesa0
libegl-mesa0:
  Installed: 18.2.2-0ubuntu1~18.04.1
  Candidate: 18.2.2-0ubuntu1~18.04.1
  Version table:
 *** 18.2.2-0ubuntu1~18.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 
Packages
100 /var/lib/dpkg/status
 18.0.5-0ubuntu0~18.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 
Packages
 18.0.0~rc5-1ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
$ ./a.out 
No crash

So I can confirm that the issues is fixed in bionic-proposed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1776499

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend

[Yogish Kulkarni]

Okay. Looks like this is the case for mutter-3.30.1. In the current
version in bionic mutter-3.28.3, I don't see "Wayland EGLStream:
${have_wayland_eglstream}" option in configure.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1805444

Title:
  [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with
  EGLDevice backend

Status in mutter package in Ubuntu:
  New

Bug description:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend due to following missing changes in mutter
  3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend

[Yogish Kulkarni]

I think on aarch64 mutter is compiled with EGLDevice backend enabled. I
have opened this bug NVIDIA Tegra SoC.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1805444

Title:
  [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with
  EGLDevice backend

Status in mutter package in Ubuntu:
  New

Bug description:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend due to following missing changes in mutter
  3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1805444] [NEW] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend

[Yogish Kulkarni]

Public bug reported:

Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
backend due to following missing changes in mutter
3.28.3-2~ubuntu18.04.2

commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
Author: Miguel A. Vico 
Date:   Thu Jun 7 16:29:44 2018 -0700

renderer/native: Choose first EGL config for non-GBM backends

Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
However, there won't be any EGL config satisfying such criteria for
non-GBM backends, such as EGLDevice.

This change will let us choose the first EGL config for the EGLDevice
backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
one.

Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
Author: Jonas Ådahl 
Date:   Tue Nov 14 16:08:52 2017 +0800

renderer/native: Also wrap flip closures for EGLStreams

When using the EGLStream backend, the MetaRendererNative passed a
GClosure to KMS when using EGLStreams, but KMS flip callback event
handler in meta-gpu-kms.c expected a closure wrapped in a closure
container, meaning it'd instead crash when using EGLStreams. Make the
flip handler get what it expects also when using EGLStreams by wrapping
the flip closure in the container before handing it over to EGL.

https://bugzilla.gnome.org/show_bug.cgi?id=790316

apt-cache policy mutter
mutter:
Installed: 3.28.3-2~ubuntu18.04.2
Candidate: 3.28.3-2~ubuntu18.04.2
Version table:
*** 3.28.3-2~ubuntu18.04.2 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
100 /var/lib/dpkg/status
3.28.1-1ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic upgrade-software-version

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1805444

Title:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend

Status in mutter package in Ubuntu:
  New

Bug description:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend due to following missing changes in mutter
  3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

[Yogish Kulkarni]

Hi Timo,
It seems -proposed "18.0.5-0ubuntu0~18.04.1" is migrated to -updates. So, is it 
possible to fix this in next version getting finalized for -updates ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1776499

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  New

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1782285] Re: Add missing libGLESv1_CM.so to Bionic

[Yogish Kulkarni]

Verified that libGLESv1_CM.so gets installed after installing libglvnd0
from bionic-proposed.

To upgrade libglvnd0, I did following:
1) Add "deb http://ports.ubuntu.com/ubuntu-ports bionic-proposed restricted 
main multiverse universe" in /etc/apt/sources.list
2) sudo apt-get update
3) sudo apt-get install --only-upgrade libglvnd0


After doing above verified that libGLESv1_CM.so get installed:
$ ls -lh /usr/lib/aarch64-linux-gnu/libGLESv1*
lrwxrwxrwx 1 root root   21 Aug 15 06:20 
/usr/lib/aarch64-linux-gnu/libGLESv1_CM.so -> libGLESv1_CM.so.1.0.0
lrwxrwxrwx 1 root root   21 Aug 15 06:20 
/usr/lib/aarch64-linux-gnu/libGLESv1_CM.so.1 -> libGLESv1_CM.so.1.0.0
-rw-r--r-- 1 root root 139K Aug 15 06:20 
/usr/lib/aarch64-linux-gnu/libGLESv1_CM.so.1.0.0

libglvnd version that was verified to have libGLESv1_CM.so:
$ apt-cache policy libglvnd0
libglvnd0:
  Installed: 1.0.0-2ubuntu2.2
  Candidate: 1.0.0-2ubuntu2.2
  Version table:
 *** 1.0.0-2ubuntu2.2 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 
Packages
100 /var/lib/dpkg/status
 1.0.0-2ubuntu2.1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 
Packages
 1.0.0-2ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages


** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1782285

Title:
  Add missing libGLESv1_CM.so to Bionic

Status in libglvnd package in Ubuntu:
  Fix Released
Status in libglvnd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  GLESv1 support was not enabled in libglvnd

  [Test case]
  install libgles1, see that the library is available

  [Regression potential]
  none, it's a new package

  --

  libGLESv1_CM.so is provided by GLVND project. This binary is missing
  in Bionic. It is also not listed under libglvnd source package in
  Bionic: https://launchpad.net/ubuntu/bionic/+source/libglvnd

  This bug is to know if this was unintentional ? in that case can it be
  generated for Bionic-updates ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1782285] [NEW] Add missing libGLESv1_CM.so to Bionic

[Yogish Kulkarni]

Public bug reported:

libGLESv1_CM.so is provided by GLVND project. This binary is missing in
Bionic. It is also not listed under libglvnd source package in Bionic:
https://launchpad.net/ubuntu/bionic/+source/libglvnd

This bug is to know if this was unintentional ? in that case can it be
generated for Bionic-updates ?

** Affects: libglvnd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic upgrade-software-version

** Package changed: mesa (Ubuntu) => libglvnd (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1782285

Title:
  Add missing libGLESv1_CM.so to Bionic

Status in libglvnd package in Ubuntu:
  New

Bug description:
  libGLESv1_CM.so is provided by GLVND project. This binary is missing
  in Bionic. It is also not listed under libglvnd source package in
  Bionic: https://launchpad.net/ubuntu/bionic/+source/libglvnd

  This bug is to know if this was unintentional ? in that case can it be
  generated for Bionic-updates ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

[Yogish Kulkarni]

Hi Timo,
Is the fix for this issue likely to backported to Bionic ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1776499

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  New

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

[Yogish Kulkarni]

Crash can be reproduced by simple test application which does e.g. :
main()
{ 
   eglGetProcAddress("egl148546488546404");
}

The problem is in the search algorithm used in mesa to look for the name
passed to eglGetProcAddress. So crash can reproduce with other names as
well. Please note that this bug will affect even though mesa driver is
actually not getting used. GLVD tries to load drivers from all vendors
listed in "/usr/share/glvnd/egl_vendor.d/". As a work around
"/usr/share/glvnd/egl_vendor.d/50_mesa.json" needs to be removed for
using EGL driver from other vendors e.g. nvidia.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1776499

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

[Yogish Kulkarni]

Sorry, I couldn't understand what do you mean by distro patch. Do you
mean it needs to be applied as patch over the current version of libegl-
mesa0 in Bionic and libegl-mesa0 generated with this patch needs to come
as upgrade in Bionic (i.e when I do apt-get upgrade) ? thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1776499

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1776499] [NEW] Crash in libegl-mesa0 due to out of bound array access

[Yogish Kulkarni]

Public bug reported:

Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
on Mesa master branch with change:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
.This bug is to request to include this change in Mesa upgrades in
bionic.

Please let me know if this change needs to be back ported to other
branch so that libegl-mesa0 upgrade in Bionic could pick this change.

lsb_release -a
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic

apt-cache policy libegl-mesa0
libegl-mesa0:
  Installed: 18.0.0~rc5-1ubuntu1
  Candidate: 18.0.0~rc5-1ubuntu1
  Version table:
 *** 18.0.0~rc5-1ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
100 /var/lib/dpkg/status

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic upgrade-software-version

** Package changed: libglvnd (Ubuntu) => mesa (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1776499

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  New

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp