No libGLESv1_CM.so symlink present

Bug #1749766 reported by a1batross
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

libGLESv1_CM.so is a common name for any GLESv1 implementation library.

I see, that libGL.so implements GLESv1, but software mostly don't consider about this library naming. For example, SDL2 tries to find GLESv1 implementation in libGLESv1_CM.so and it just shows me a error like: "Could not initialize OpenGL / GLES library".

SDL2 isn't the only, there is many other possible code, which doesn't know that libGL.so.1 implements GLES interface.

Meanwhile, libGLESv1_CM.so present only in nvidia-* driver package.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libglapi-mesa 17.2.4-0ubuntu1~17.10.2
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Feb 15 20:36:48 2018
Dependencies:
 gcc-7-base 7.2.0-8ubuntu3
 libc6 2.26-0ubuntu2.1
 libgcc1 1:7.2.0-8ubuntu3
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
 nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
InstallationDate: Installed on 2017-12-06 (71 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20354
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=b1945f5a-569f-437a-8562-73446b5a924e ro quiet splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 9BCN91WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A5
dmi.board.vendor: LENOVO
dmi.board.version: 31900059WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z50-70
dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20354
dmi.product.version: Lenovo Z50-70
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Revision history for this message
a1batross (a1ba-omarov) wrote :
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

GLESv1 support was dropped quite some time ago.

Changed in mesa (Ubuntu):
status: New → Invalid
Revision history for this message
a1batross (a1ba-omarov) wrote :

Thanks for the answer!

When and why it was dropped, while drivers still have GLES1 calls inside binary? Mesa's libGL.so still does have them.

Proprietary drivers also don't drop GLES1 support, GLES1 functionality persists in latest NVidia driver.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.