Flatpak Applications failing to start

Good day to you all!

It’s my first post on the forums, so I apologize in advance for any mistakes in etiquette.

I’m on an up-to-date installation of Tumbleweed, running KDE in X11, and using an nvidia card on the 550.100 drivers distributed by the “official” nvidia repo.

Is anyone else having problems with flatpak apps failing to initialize?
Several flatpak apps began having issues launching, they are:

Telegram (org.telegram.desktop)

  • which launches but shows an error;
    image

Plex (tv.plex.PlexDesktop)

  • silently crashes;

ZapZap (com.rtosta.zapzap)

  • silently crashes;

The problem began yesterday, but I wasn’t paying enough attention to see what broke it.

It certainly is related to flatpak, as to check I booted from a few snapshots, one from yesterday morning, one from three days ago, and one from a week ago, and the flatpaks apps were having issues there too. Did flathub screw an update? Or did I do something that broke OpenGL in flatpak?

Here’s my flatpak list output (on pastebin)

I’ve already tried flatpak repair, and removing and reinstalling the offending flatpaks and their dependencies…

I am usually able to solve problems on my own, but for this one I’m stumped.

Thank you in advance for your attention!

@alghost Hi, maybe Mesa related? I’m assuming the flatpaks are installed as your user? If you open a terminal and use for example flatpak run org.telegram.desktop what do you see in the output.

Check configuration of the flatpak via Flatseal.

Thanks for the quick response!

After reenabling OpenGL on telegram (as it works if I disable it) the terminal output the following:

qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize 0, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 0, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize 0, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 0, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize 0, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 0, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)
Could not initialize GLX

ZapZap gives a very similar error:

qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize 0, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 0, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize 0, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 0, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize 0, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 0, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)
Could not initialize GLX

Have you seen something like this before?

Sorry for the double post, but I’m leaving this for posterity:

The problem was caused by flathub that pushed a botched org.freedesktop.Platform.GL.nvidia-550-100 update. I just ran flatpak update again, and the above package had an update, which fixed everything I described.

Hooray! And thanks for your attention.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.