Libgl Error Failed To Load Driver Radeonsi

[Vittoria Pretlow]

AFAIKthis is only available to the system if AMDGPU is loaded. The PRO drivers do not seem to use this and it crashes out. Is this hard-coded into KiCad, or is the error coming from the driver itself? Can it be resolved.

Looks to be a driver issue. Googling by that error message there are other reports on other softwares.

You may try to run KiCad in the command line

$ LIBGL_ALWAYS_SOFTWARE=1 kicad

and see if it runs openGL in software mode.

So seems that the AMDGPU-PRO driver is not playing very nice with the system. I could try going back to the fully open-source drivers and see if this all resolves. However I posted to AMD about the issue and I will probably wait and see if they have any comments.

Aidan

PLEASE READ: don't email me to report bugs, unless you are sure it's a packaging bug. Not only is email not a good tool for tracking bugs, it also excludes anybody else from tracking or working on the issue. Please read the section "Debugging and...

Although googling this seems to reveal that perhaps this is not entirely true. To say that this is rather convoluted is an under statement. But I see folks doing all sorts of funky stuff to try and get this working. I remember having troubles in the past trying to patch together a functional graphics driver environment and to be honest, it was not pretty.

To answer your question about other OpenGL software. Yes!! and very much a yes. I of course ran glxgears and received no errors. I also then ran some heavier tests using other kinda gaming oriented test suites and all seemed happy and report no problems with GL.

If you found that it works on other OpenGL applications but not on KiCad, I suggest you create an issue in launchpad ( check the kicad website how to create a bug report ) and give a link to this thread and as much information as possible.

Oh dear. It seems my choice is now being made for me. If I want to run Kicad that is.

Having just re-installed the AMDGPU-PRO 18.30 driver. I now crash out of Kicad (actually gerbview without warning and pcbnew if I try acceleration) with the following:

libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: radeonsi

mesa: for the -simplifycfg-sink-common option: may only occur zero or one times!

libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: radeonsi

libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: swrast

Segmentation fault (core dumped)

Hi,

A quick update. I have worked around the issue by installing the AMDGPU-PRO driver using the --headless option. This installs AMDs kernel modules but AFAIK keeps the OpenGL implementation using the Ubuntu maintainers code base, as well as other things like Mesa and acceleration. OpenCL however uses the AMD driver and works as expected. Therefore I now have all applications playing together.

Thanks for the suggestions, but I think I will stay with my current set-up. I think it makes sense, everything seems to be working and AFAIK it stays as close as possible to the fully open driver configuration. Though to be honest I am not quite sure whos code is doing what.

AMD say that the configuration I have opted for uses:

Base kernel drivers ( no accelerated graphics drivers) + Pro OpenCL (headless mode)

I read briefly that some functions of pcbnew actually require OpenGL to function, cant remember what that was, maybe you could give me some suggestions about how to thoroughly test the KiCad features against my current OpenGL configuration.

you have recently upgraded your system, including updates to critical parts of the system (e.g. the kernel), but not yet rebooted. This may cause issues as the version of nouveau kernel module that the system is trying to load no longer matches the version of the running kernel exactly - and the system is very strict about ensuring an exact match. This would be easily fixed by a reboot.

I figured out the problem I was having earlier involving the ./config command, but then bumped into another when I attempted ./build. It is remarkably similar to the one posted above, except on the Mac platform. Here is the error message given in the terminal:

This is definitely the issue/ I just went over the .configure file (pasted below) and it seems that the computer is calling an old version of Qt (4.8.7) which is odd because I can navigate into that directory and I have Qt 5.7 installed. I suppose trying to locate the old version and uninstall followed by reconfiguring will be the best next logical step.

I use Ubuntu22.04.02 and I meet this issue today. After checking, I found this solution salck libgl. By installing this package conda install -c conda-forge libstdcxx-ng, I get rid of the error magically.

wine: cannot find L"C:\windows\system32\winemenubuilder.exe" ATTENTION: default value of option mesa_glthread overridden by environment. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: radeonsi ATTENTION: default value of option mesa_glthread overridden by environment. mesa: for the -simplifycfg-sink-common option: may only occur zero or one times! libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: radeonsi ATTENTION: default value of option mesa_glthread overridden by environment. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swras

reverted the kernel (I was on v4.18.12). graphical bug still present.

the Lutris log still says the following: ATTENTION: default value of option mesa_glthread overridden by environment.

libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: radeonsi

ATTENTION: default value of option mesa_glthread overridden by environment.

mesa: for the -simplifycfg-sink-common option: may only occur zero or one times!

libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: radeonsi

ATTENTION: default value of option mesa_glthread overridden by environment.

libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: swrast

After that, log out and back in as said user. Steam should detect the controller without issue. A good way to test this is to make sure Steam has focus and press the PlayStation button. If Big Picture mode starts, the controller is detected and configured correctly.

The easiest workaround is to click and dismiss any notification after steam has launched. It has been reported that using a custom skin for steam that disables notification animations resolves this issue for some (but not all) users.

Next, ensure that the user running Steam has sufficient permissions to access direct rendering. If the USE variable is set to acl and elogind or systemd is being used, permissions will be handled automatically. Otherwise, add the user running Steam to the video group:

If direct rendering is enabled and the correct OpenGL implementation is selected, then this issue may be caused by app-eselect/eselect-opengl 1.3*.[2]. This issue has been fixed for users of the steam-launcher ebuild. Otherwise, run the following as a temporary workaround:

When installing the Flatpak version, certain items may show "Invalid SSL certificate" when trying to load (like News and Friends). This is caused by a bug in app-crypt/p11-kit. Make sure the version of app-crypt/p11-kit is equal to or greater than 0.23.20.

After updating x11-drivers/nvidia-drivers, Proton and Vulkan-based games may fail to work (fallback to OpenGL). On a laptop with multiple GPUs, Proton/Vulkan games use the integrated GPU instead of the NVIDIA discrete GPU after updating x11-drivers/nvidia-drivers.

This issue[4] is likely due to a driver version mismatch. Flatpak applications run within a container (or "sandbox"), and the NVIDIA libraries within the container must match the drivers loaded and running on the Gentoo host.

to update the required runtime for com.valvesoftware.Steam. Check if flatpak updates the org.freedesktop.Platform.GL[32].nvidia-VERSION-NUM package to match the version number of x11-drivers/nvidia-drivers on the Gentoo host.

When running Steam in the GNOME desktop environment the store (and special offers) no longer properly render; the friend's list is constantly in an offline state and status cannot be changed to online. When viewing Steam client debugging output, the following line is repeatably displayed:

The issue is caused by Steam not properly setting the GSETTINGS_BACKEND environment variable, not setting the GIO_MODULE_DIR environment variable to its own GIO/modules path, and not shipping a newer version of glib library in its included runtime.

The workaround is to set the GSETTINGS_BACKEND environment variable to memory when launching Steam[5][6]. This is best completed by editing the Exec line in the steam.desktop file used to launch Steam:

However, this results in Bash failing to run. It is also a security issue, and it is strongly recommended to try without PaX marking. If it works when using the proprietary NVIDIA drivers, please make a note of it on this page.

The Steam runtime overrides various system libraries, including libgcc, libstdc++, and libgpg-error with its own bundled versions[8]. This can result in Steam failing to start with the following error:

Repeat the above to discover other problematic libraries in the Steam runtime. The bundled libraries may reappear after every Steam update. In this case simply delete the libraries again from the Steam runtime.

If an X cursor theme has not been set by the desktop environment or window manager, Steam will override the default X cursor theme. This can result in a reversed X cursor from left to right. The issue can be fixed by setting an X cursor theme, if one is available, or by installing an X cursor theme:

Selecting the Remember my password option at the Steam login dialog when Steam is running without D-Bus, will cause Steam to segfault the next time it is started[10]. This issue can be fixed by running the following:

3a8082e126