Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symbol lookup error: undefined symbol: glEGLImageTargetTexStorageEXT #932

Closed
Shamaoke opened this issue Nov 20, 2022 · 0 comments
Closed

Comments

@Shamaoke
Copy link

Shamaoke commented Nov 20, 2022

After the update to version 10 the program no longer starts. The previous version worked without any problems on the same graphic driver.

Platform

Arch Linux

GPU, drivers, and screen setup

NVidia GeForce 410M; nvidia-340xx-dkms; mesa 22.2.3; Sony Vaio Laptop, 2011 production year

`glxinfo -B`
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 833 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 410M/PCIe/SSE2
OpenGL core profile version string: 4.4.0 NVIDIA 340.108
OpenGL core profile shading language version string: 4.40 NVIDIA via Cg compiler
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.4.0 NVIDIA 340.108
OpenGL shading language version string: 4.40 NVIDIA via Cg compiler
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.1 NVIDIA 340.108 340.108
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

Environment

Openbox 3.6.1

picom version

picom 10

picom --version

picom: symbol lookup error: picom: undefined symbol: glEGLImageTargetTexStorageEXT

picom --diagnostics

picom: symbol lookup error: picom: undefined symbol: glEGLImageTargetTexStorageEXT

Configuration:

The program doesn't start with any settings.

Steps of reproduction

  1. Run picom;

  2. Observe the picom: symbol lookup error: picom: undefined symbol: glEGLImageTargetTexStorageEXT error.

Expected behavior

The program is functioning normally.

Current Behavior

When launching the program crashes with the error: picom: symbol lookup error: picom: undefined symbol: glEGLImageTargetTexStorageEXT.

Other details

`nm --dynamic /usr/lib/libGL.so | grep glEGLImageTargetTexStorageEXT`
0000000000049e80 T glEGLImageTargetTexStorageEXT
`ldd /usr/bin/picom`
	linux-vdso.so.1 (0x00007ffd0cfe0000)
	libm.so.6 => /usr/lib/libm.so.6 (0x00007fb99b225000)
	libev.so.4 => /usr/lib/libev.so.4 (0x00007fb99b214000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0x00007fb99b0d1000)
	libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0x00007fb99b0cc000)
	libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007fb99b0a1000)
	libxcb-render-util.so.0 => /usr/lib/libxcb-render-util.so.0 (0x00007fb99b09b000)
	libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00007fb99b08a000)
	libxcb-image.so.0 => /usr/lib/libxcb-image.so.0 (0x00007fb99b084000)
	libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00007fb99afd7000)
	libxcb-damage.so.0 => /usr/lib/libxcb-damage.so.0 (0x00007fb99afd2000)
	libxcb-randr.so.0 => /usr/lib/libxcb-randr.so.0 (0x00007fb99afc0000)
	libxcb-sync.so.1 => /usr/lib/libxcb-sync.so.1 (0x00007fb99afb7000)
	libxcb-composite.so.0 => /usr/lib/libxcb-composite.so.0 (0x00007fb99afb0000)
	libxcb-shape.so.0 => /usr/lib/libxcb-shape.so.0 (0x00007fb99afaa000)
	libxcb-xinerama.so.0 => /usr/lib/libxcb-xinerama.so.0 (0x00007fb99afa5000)
	libxcb-xfixes.so.0 => /usr/lib/libxcb-xfixes.so.0 (0x00007fb99af9c000)
	libxcb-present.so.0 => /usr/lib/libxcb-present.so.0 (0x00007fb99af97000)
	libxcb-glx.so.0 => /usr/lib/libxcb-glx.so.0 (0x00007fb99af7a000)
	libconfig.so.11 => /usr/lib/libconfig.so.11 (0x00007fb99af69000)
	libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007fb99aeef000)
	libGL.so.1 => /usr/lib/nvidia/libGL.so.1 (0x00007fb99aa00000)
	libEGL.so.1 => /usr/lib/nvidia/libEGL.so.1 (0x00007fb99a600000)
	libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007fb99ae9e000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fb99ae7e000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007fb99a419000)
	/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fb99b399000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0x00007fb99ae77000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007fb99ae6f000)
	libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x00007fb99ae6a000)
	libxcb-util.so.1 => /usr/lib/libxcb-util.so.1 (0x00007fb99ae62000)
	libnvidia-tls.so.340.108 => /usr/lib/nvidia/libnvidia-tls.so.340.108 (0x00007fb99a200000)
	libnvidia-glcore.so.340.108 => /usr/lib/nvidia/libnvidia-glcore.so.340.108 (0x00007fb997400000)
	libXext.so.6 => /usr/lib/libXext.so.6 (0x00007fb99ae4b000)
	libdl.so.2 => /usr/lib/libdl.so.2 (0x00007fb99ae46000)
	libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007fb99ae41000)
	librt.so.1 => /usr/lib/librt.so.1 (0x00007fb99ae3c000)
	libnvidia-glsi.so.340.108 => /usr/lib/nvidia/libnvidia-glsi.so.340.108 (0x00007fb997000000)
	libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0x00007fb99ad5e000)
	libcap.so.2 => /usr/lib/libcap.so.2 (0x00007fb99ad52000)
	libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007fb99a0b8000)
	liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007fb99a9d6000)
	libzstd.so.1 => /usr/lib/libzstd.so.1 (0x00007fb99a92d000)
	liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007fb99a90b000)
	libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007fb99a092000)
`nm --dynamic /usr/lib/nvidia/libGL.so.340.108 | grep glEGLImageTargetTexStorageEXT`
no output
@yshui yshui closed this as completed in 2d35f78 Nov 22, 2022
bmwiedemann pushed a commit to bmwiedemann/openSUSE that referenced this issue Nov 23, 2022
https://build.opensuse.org/request/show/1037427
by user mia + dimstar_suse
- Update to version 10.1
Fixes:
  * A GL texture leak, related to
    gh#yshui/picom#892
  * A crash when shadow radius is set to 0
    gh#yshui/picom#927
  * An undefined symbol error
    gh#yshui/picom#932
FT-Labs pushed a commit to FT-Labs/picom that referenced this issue Jan 23, 2023
FT-Labs pushed a commit to FT-Labs/picom that referenced this issue Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant