Having these issues when attempting to run these apps under Wayland:
RSS Guard:
time=" 0.012" type="info" -> Could not load the Qt platform plugin "wayland" in "" even though it was found.
Kodi:
F: Not sharing "/usr/bin" with sandbox: Path "/usr" is reserved by Flatpak
'this->recurse > 0' failed at ../src/pipewire/thread-loop.c:63 do_unlock()
libva info: VA-API version 1.19.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/GL/lib/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_19
libva info: va_openDriver() returns 0
amdgpu: amdgpu_cs_ctx_create2 failed. (-13)
/app/bin/kodi: line 216: 7 Segmentation fault (core dumped) ${KODI_BINARY} ${ENV_ARGS} $SAVED_ARGS
Crash report available at /home/user/.var/app/tv.kodi.Kodi/data/kodi_crashlog-20241215_015945.log
Librewolf:
Exiting due to channel error.
But when I go back to X11, they open normally.
Seems like one of the updates here caused this problem:
But I don’t know which one.
Confirmed to be a Mesa issue with flatpak.
Had to use an environment variable to make Librewolf work like so:
FLATPAK_GL_DRIVERS=24.2.5 flatpak run io.gitlab.librewolf-community
Now I wonder what is the best way to revert Mesa for Flatpak.
Hopefully, this update is reverted quickly.
1 Like
Reverting to previous commits before the latest one fixed the issue with Mesa problems.
As root (for all apps installed for all users)
sudo flatpak update --commit=0afe3466c4abe98c6d77d6740f69fa18c9940e851176d3114903777f91469455 org.freedesktop.Platform.GL.default/x86_64/24.08
sudo flatpak update --commit=0417ef24351ecbb9208216510d7190ce94aa483f812b713b9b00e4ff5987b968 org.freedesktop.Platform.GL.default/x86_64/23.08
sudo flatpak update --commit=d64b09e6ab6999efdda4a655853cfca8432335ff680d0072793433d957ee3921 org.freedesktop.Platform.GL.default/x86_64/23.08-extra
sudo flatpak update --commit=10a5153b2b4aee357d43cecf7987ee972acd2d3d282b0f2e317c9caa4fd27c8c org.freedesktop.Platform.GL.default/x86_64/24.08extra
sudo flatpak update --commit=2ddc90b5171b59971b45a88a0c328cd25b9c7e43599d248dcafc02ead3692bbc org.freedesktop.Platform.GL32.default/x86_64/23.08
sudo flatpak update --commit=daf1c7f6106ab9cfd9a0c4df19dfca946cfbd187c27c7fd60131b42c02f770e4 org.freedesktop.Platform.GL32.default/x86_64/24.08
sudo flatpak update --commit=0417ef24351ecbb9208216510d7190ce94aa483f812b713b9b00e4ff5987b968 org.freedesktop.Platform.GL.default/x86_64/23.08
As user (if any apps are installed for the user only)
flatpak update --commit=0afe3466c4abe98c6d77d6740f69fa18c9940e851176d3114903777f91469455 org.freedesktop.Platform.GL.default/x86_64/24.08
flatpak update --commit=0417ef24351ecbb9208216510d7190ce94aa483f812b713b9b00e4ff5987b968 org.freedesktop.Platform.GL.default/x86_64/23.08
flatpak update --commit=d64b09e6ab6999efdda4a655853cfca8432335ff680d0072793433d957ee3921 org.freedesktop.Platform.GL.default/x86_64/23.08-extra
flatpak update --commit=10a5153b2b4aee357d43cecf7987ee972acd2d3d282b0f2e317c9caa4fd27c8c org.freedesktop.Platform.GL.default/x86_64/24.08extra
flatpak update --commit=2ddc90b5171b59971b45a88a0c328cd25b9c7e43599d248dcafc02ead3692bbc org.freedesktop.Platform.GL32.default/x86_64/23.08
flatpak update --commit=daf1c7f6106ab9cfd9a0c4df19dfca946cfbd187c27c7fd60131b42c02f770e4 org.freedesktop.Platform.GL32.default/x86_64/24.08
flatpak update --commit=0417ef24351ecbb9208216510d7190ce94aa483f812b713b9b00e4ff5987b968 org.freedesktop.Platform.GL.default/x86_64/23.08
Oh… My god. What a pain. Think I’ll have to update just once a week instead.
But at least I can say depending mostly on Flatpak apps has spared me from having a system were the desktop is completely broken due broken packaging. Rendering the system unusable. So, I’ll give Flatpak a pass. At least it’s easily revert-able.
1 Like
