Bug 25555 - Installing nvidia-current breaks some OpenGL applications on Mageia 7.1 using GeForce 750Ti GPU
Summary: Installing nvidia-current breaks some OpenGL applications on Mageia 7.1 using...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-13 00:15 CEST by Wade Brandis
Modified: 2021-09-07 14:10 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Wade Brandis 2019-10-13 00:15:01 CEST
Hello.

I have been using Mageia 7.1 for about the last month, and I think I may have found a bug that occurs whenever I install the proprietary nvidia-current driver for my PC's GeForce 750Ti GPU. I'm currently running KDE Plasma 5, but I also encountered this issue using XFCE.

I used Mageia Control Center to configure and install the driver. The driver installs fine. However, certain applications that use OpenGL fail to launch when using the proprietary Nvidia driver, giving a LibGL.so error in the terminal. These applications do work as normal when the nouveau driver is used. Below is the output from projectM-pulseaudio after switching to the nvidia-current driver:
-------------------------------
[--REDACTED--@localhost ~]$ projectM-pulseaudio
dir:/usr/share/projectM/config.inp 
reading ~/.projectM/config.inp 
kf5.kio.core: "Could not enter folder tags:/."
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast

Similar errors occur with qv4l2, which I use to configure my Dazzle DVC100 analog video capture device. 

I can fix the error by using a solution I found on the Ubuntu forums that outline an almost identical issue. 
https://askubuntu.com/questions/834254/steam-libgl-error-no-matching-fbconfigs-or-visuals-found-libgl-error-failed-t/1154964

It appears my OpenGL applications I use on my Mageia installation are still trying to use the old libGL.so when they are supposed to use nvidia's libGL.so. Here is the terminal output from running the "ldconfig" command outlined in the forum posting:
-------------------

[root@localhost --REDACTED--]# ldconfig -p | grep -i gl.so
        libwayland-egl.so.1 (libc6,x86-64) => /lib64/libwayland-egl.so.1
        libQt5OpenGL.so.5 (libc6,x86-64) => /lib64/libQt5OpenGL.so.5
        libOpenGL.so.0 (libc6,x86-64) => /usr/lib64/nvidia-current/libOpenGL.so.0
        libOpenGL.so.0 (libc6) => /usr/lib/nvidia-current/libOpenGL.so.0
        libGL.so.1 (libc6,x86-64) => /usr/lib64/nvidia-current/libGL.so.1
        libGL.so.1 (libc6,x86-64) => /lib64/libGL.so.1
        libGL.so.1 (libc6) => /usr/lib/nvidia-current/libGL.so.1
        libEGL.so.1 (libc6,x86-64) => /usr/lib64/nvidia-current/libEGL.so.1
        libEGL.so.1 (libc6,x86-64) => /lib64/libEGL.so.1
        libEGL.so.1 (libc6) => /usr/lib/nvidia-current/libEGL.so.1

If I delete the libgGL.so.1 symlink in the /lib64 folder, qv4l2 starts working again. I also experience no other issues running other OpenGL applications or games, and Mageia runs smooth and stable.

I don't know if this is a specific bug with my computer, or an issue with the particular nvidia-current packages.
Comment 1 Lewis Smith 2019-10-14 10:52:50 CEST
Thank you Wade for your detailed & helpful report.

This looks similar to bug 25204 (NVIDIA GP102 [GeForce GTX 1080 Ti]), but I cannot say they are effectively duplicates - the same problem. If they are, please mark this bug as a duplicate of the older one.

Assigning similarly to the kernel/drivers people.

Assignee: bugsquad => kernel

Comment 2 Aurelien Oudelet 2021-07-06 13:15:49 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 3 Marja Van Waes 2021-09-07 14:10:44 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Resolution: (none) => OLD
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.