Your message dated Wed, 15 Jul 2026 09:48:33 +0100
with message-id <[email protected]>
and subject line Re: Bug#1021170: libegl-mesa0: Extra \$ in libEGL_mesa.so.0.0.0
has caused the Debian Bug report #1021168,
regarding libgbm1: Extra \$ in libgbm.so.1.0.0
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 [email protected]
immediately.)
--
1021168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021168
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgbm1
Version: 20.3.5-1
Severity: important
File: /usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0
Dear Maintainer,
When testing version 2019.1 of the Schrödinger suite we found a bug in 3 of the
packages belonging to Mesa; libgbm1, libglx-mesa0 and libegl-mesa0 (reported as
separat bugs)
We got the following error message
libGL error: MESA-LOADER: failed to open swrast:
/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or
directory (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast
The '\$' preceding '${ORIGIN}' does not seem right.
After running a script that checked all files in /lib, /lib64, /usr/lib and
/usr/libexec
we found 3 files containing the string '\$${ORIGIN}/dri'.
/usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0 (from libgbm1/now 20.3.5-1 amd64)
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0 (from libglx-mesa0/now
20.3.5-1 amd64)
/usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0.0.0 (from libegl-mesa0/now
20.3.5-1 amd64)
The string is compiled inte the lib itself, it is not found in the ELF-header.
The easiest way to check if the bug is present is with
grep -a '\\\$\$\{ORIGIN\}/dri' <lib>
We have tested a binary patch as follows:
cd /usr/lib/x86_64-linux-gnu
cp -p libgbm.so.1.0.0 libgbm.so.1.0.0.ORIG
cat libgbm.so.1.0.0.ORIG | sed -e 's/:\\$${ORIGIN}\/dri:/:\/:${ORIGIN}\/dri:/'
> libgbm.so.1.0.0
(and corresponding to the files from the two other packages).
With that patchs we can start the Schrödinger suite without any errors. Other
software that we have tried and that use Mesa also work without complaint after
we patched.
The occurrence of $$ is found in the newer version 22.2.0-1 as well.
-- System Information:
Debian Release: 11.1
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-0.deb11.4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages libgbm1:amd64 depends on:
ii libc6 2.31-13+deb11u4
ii libdrm2 2.4.104-1
ii libexpat1 2.2.10-2+deb11u4
ii libwayland-server0 1.18.0-2~exp1.1
libgbm1:amd64 recommends no packages.
libgbm1:amd64 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.0.7-2
On Mon, 03 Oct 2022 at 09:22:28 +0000, Erik Larsson wrote:
When testing version 2019.1 of the Schrödinger suite we found a bug in 3 of the
packages belonging to Mesa; libgbm1, libglx-mesa0 and libegl-mesa0 (reported as
separat bugs)
We got the following error message
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so:
cannot open shared object file: No such file or directory (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast
The '\$' preceding '${ORIGIN}' does not seem right.
The Mesa in Debian 13 no longer uses ${ORIGIN} in this way.
This issue was originally reported against Debian 11, which is partially
supported by the Debian LTS team (mostly security fixes only) until
2026-08-31, but no longer maintained by the Debian project.
It appears that this issue also still affects Debian 12, which again is
partially supported by the Debian LTS team but is no longer maintained
by the Debian project.
smcv
--- End Message ---
