Possible libmesa regression: `info.separate_shader` fixed upstream

Asked by David Vereb

I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled into debian's repo. I do not know the proper way to request an updated version be made for Ubuntu. I've manually installed many different versions of libmesa to test on my own that it was working in an older version, is broken in this update, and was fixed again in 22.3.4 and 22.3.5.

The one-line fix is implemented here in libmesa's repo: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782/pipelines

Unfortunately I'm not using libmesa directly. I'm programming an application using fox-toolkit which interfaces with libmesa behind the scenes for me. I reported my issue to them first, and they stated it appears to be in the mesa library, which is what ultimately led me down the path to their repo, debian's repo, and here. Please let me know if I'm in the right spot, and, if so, what my next step is to properly report this.

Thank you for your time. Let me know if you need any additional information aside from what I've included below.

 > lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04

 > apt-cache policy libglx-mesa0
libglx-mesa0:
  Installed: 22.2.5-0ubuntu0.1~22.04.1
  Candidate: 22.2.5-0ubuntu0.1~22.04.1
  Version table:
 *** 22.2.5-0ubuntu0.1~22.04.1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     22.0.1-1ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz

OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CML GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.2.5
OpenGL core profile shading language version string: 4.60

WORKS WITH:
sudo apt install libglx-mesa0=22.0.1-1ubuntu2 libglapi-mesa=22.0.1-1ubuntu2 libegl-mesa0=22.0.1-1ubuntu2 libgbm1=22.0.1-1ubuntu2 libgl1-mesa-dri=22.0.1-1ubuntu2

BROKEN WHEN UPDATED:
sudo apt install libglx-mesa0 libglapi-mesa libegl-mesa0 libgbm1 libgl1-mesa-dri

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Bernard Stafford
Solved:
Last query:
Last reply:
Revision history for this message
Bernard Stafford (bernard010) said :
#1

Package: libglx-mesa0 (22.2.5-0ubuntu0.1~22.04.1) is available on Jammy Updates.
https://packages.ubuntu.com/jammy-updates/libglx-mesa0

Revision history for this message
David Vereb (dvereb) said :
#2

Yes, when my PC updated to this most recent version the bug showed up. It works again if I downgrade away from this version, but I'm wondering if it's possible to request an even newer version that would take the upstream bugfix that has since been released.

If so, what is the proper way to make this request?
If not, is there a way to track when the package is planning on updating in the future so I know when I can unpin the package from the older version?

Revision history for this message
Best Bernard Stafford (bernard010) said (last edit ):
#3

Yes their is.
File a bug report as a "feature request"
Open a terminal [ctl+a;t+t] type:
ubuntu-bug libglx-mesa0

This will start Apport to collect extra information to add to your bug report.
Otherwise bug report will be invalid.
Debian has libglx-mesa0 (20.3.5-1~bpo10+1)
https://packages.debian.org/buster-backports/libglx-mesa0
Which has not been backported or available for Jammy updates.

Revision history for this message
David Vereb (dvereb) said :
#4

I've linked that bug request to this thread. I did not see a place to mark it as a feature request, so I added "[feature request]" to the title.

I'm not sure how you decided it was libglx-mesa0, and not one of the other packages that had to be upgraded along side it, such as libgl1-mesa-dri, but I assume it's all so closely related that it might not matter which one it's attached to?

I'm also curious if it should be labeled as [regression] since it did work in a previous version, but I'll wait & see what response I receive from the bug report.

Thanks again!

Revision history for this message
David Vereb (dvereb) said :
#5

Thanks Bernard Stafford, that solved my question.