[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2021-11-07 Thread Maniraj D
Hi Timo, A similar crash is observed in mesa-egl and it is resolved in Mesa master branch. Please refer the bug: https://bugs.launchpad.net/mesa/+bug/1946621 Can you help backporting the fix to "Focal" series. -- You received this bug notification because you are a member of Ubuntu-X, which is

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2021-09-28 Thread Timo Aaltonen
huh, focal-updates has a much newer mesa which has that commit.. -- You received this bug notification because you are a member of Ubuntu-X, 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 To manage n

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2021-09-28 Thread Penny Chiu
This issue is still happened using focal-update. I checked below changelog for libegl-mesa0 package: - https://packages.ubuntu.com/focal/libegl-mesa0 - https://packages.ubuntu.com/focal-updates/libegl-mesa0 And found the change is only existed in focal, but not in focal-update: mesa (18.1.1-1ub

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2019-01-31 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1 --- mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Thu, 29 No

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2019-01-30 Thread Timo Aaltonen
before 18.04.2 is released, which means before feb 7th unless it's delayed thanks for verifying! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1776499 Title: Crash in libegl-mesa0 due to out o

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2019-01-30 Thread 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 Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1776499 Title: Crash in libegl-mesa0 due to out of bound

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2019-01-30 Thread 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("egl

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2019-01-29 Thread Timo Aaltonen
please test 18.2.2 from bionic-proposed ** Changed in: mesa (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1776499 Title: Crash in libegl-mes

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-10-25 Thread Timo Aaltonen
The next one will be based on mesa 18.2.x from 18.10 -- You received this bug notification because you are a member of Ubuntu-X, 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 To manage notifications

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-10-25 Thread 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 Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-29 Thread Timo Aaltonen
yes, but not before the current version in -proposed has migrated to -updates -- You received this bug notification because you are a member of Ubuntu-X, 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

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-26 Thread 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 Ubuntu-X, 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 To manag

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-19 Thread Iain Lane
** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1776499 Title: Crash in libegl-mesa0 due to out of boun

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-13 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 18.1.1-1ubuntu1 --- mesa (18.1.1-1ubuntu1) cosmic; urgency=medium * Merge from Debian. * glvnd-fix-a-segfault-in-eglgetprocaddess.diff: Backport a commit to fix a segfault. (LP: #1776499) -- Timo Aaltonen Wed, 13 Jun 2018 12:10:21 +

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-13 Thread 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

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-13 Thread Timo Aaltonen
Yes. Problem is that bionic-proposed already has 18.0.5 staged for the 18.04.1 update, so adding more would delay getting that update. Is there a way to reproduce this bug? How common is it? I'm wondering if it should be skipped for now and provided via backport from cosmic after 18.10 is released

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-13 Thread 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 th

[Ubuntu-x-swat] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-12 Thread Timo Aaltonen
18.0.x series is done, this would need to be added as a distro patch ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bug