Description of problem: --- $ flatpak run org.gnome.Extensions libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast (gnome-extensions-app:3): Gdk-WARNING **: 10:14:35.284: The program 'gnome-extensions-app' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadFBConfig'. (Details: serial 268 error_code 167 request_code 151 (GLX) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) --- Flatpak install attributes: org.gnome.Extensions,40.0,stable,fedora,system Version-Release number of selected component (if applicable): 40.0 How reproducible: 100% of time Steps to Reproduce: 1.$ flatpak run org.gnome.Extensions 2. done. Actual results: App fails to launch on xorg. Expected results: Should launch app. Additional info: Operating System: Fedora 34.20210424.n.0 (Silverblue) CPE OS Name: cpe:/o:fedoraproject:fedora:34 Kernel: Linux 5.11.12-300.fc34.x86_64 Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad P50 Nvidia graphics: NVIDIA Corporation GM107GLM [Quadro M2000...
Can you try if it works better if you do 'flatpak run --device=dri org.gnome.Extensions' ? I suspect it may need dri access because of the switch to gtk4 that makes use of gl.
I tried using --device=dri, no success: flatpak run --device=dri org.gnome.Extensions libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast (gnome-extensions-app:3): Gdk-WARNING **: 09:10:46.514: The program 'gnome-extensions-app' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadFBConfig'. (Details: serial 260 error_code 167 request_code 151 (GLX) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
I can confirm this problem: ~ ❯❯❯ flatpak run org.gnome.Extensions libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast (gnome-extensions-app:3): Gdk-WARNING **: 07:47:33.933: The program 'gnome-extensions-app' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadFBConfig'. (Details: serial 266 error_code 167 request_code 151 (GLX) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Additional info: Kernel: 5.11.20-300.fc34.x86_64 Graphics: Nvidia, proprietary, version 465.27-1 from rpmfusion
I have the same problem on Fedora 33 (gnome 3.38.5) with flatpak org.gnome.Extensions release 40.0 $ flatpak run org.gnome.Extensions libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast (gnome-extensions-app:3): Gdk-WARNING **: 10:56:21.926: The program 'gnome-extensions-app' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadFBConfig'. (Details: serial 257 error_code 179 request_code 154 (GLX) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Additional info: Kernel: 5.12.7-200.fc33.x86_64 Graphics: nvidia, 390.143, 5.12.7-200.fc33.x86_64, x86_64: installed DKMS
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.