xdg-desktop-portal is crashing with a segfault
OS: Bazzite-GNOME-NVIDIA-Open:stable (version 42.20250522.1)
GPU: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A]
NVIDIA Driver: 4.6.0 NVIDIA 570.153.02
Kernel: 6.14.6-105.bazzite.fc42.x86_64
Screenshot of the logs are attached. This occurs when attempting to launch the file/folder picker from any chromium/electron based app. I validated this happens on my system under the following app install types:
-flatpak (both user and system context)
-appimage
-app installed inside a distrobox (tried both fedora and ubuntu distroboxes)
This also occurs even with nvidia_drm.modeset=1 added to kargs.
I tried disabling all gnome extensions.
So far I have tested this with vscode, vscodium, postman, discord, and chrome and all have the issue.
I created a new test user on my device and still had the issue.
I ran the apps with LIBGL_ALWAYS_SOFTWARE=1 to confirm it was not a GPU driver bug.
I tested on a different system running bazzite 41 and it does not have this issue. After updating that system to the latest stable version (stable-42.20250522.1) it also experiences this issue.
GPU: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A]
NVIDIA Driver: 4.6.0 NVIDIA 570.153.02
Kernel: 6.14.6-105.bazzite.fc42.x86_64
Screenshot of the logs are attached. This occurs when attempting to launch the file/folder picker from any chromium/electron based app. I validated this happens on my system under the following app install types:
-flatpak (both user and system context)
-appimage
-app installed inside a distrobox (tried both fedora and ubuntu distroboxes)
This also occurs even with nvidia_drm.modeset=1 added to kargs.
I tried disabling all gnome extensions.
So far I have tested this with vscode, vscodium, postman, discord, and chrome and all have the issue.
I created a new test user on my device and still had the issue.
I ran the apps with LIBGL_ALWAYS_SOFTWARE=1 to confirm it was not a GPU driver bug.
I tested on a different system running bazzite 41 and it does not have this issue. After updating that system to the latest stable version (stable-42.20250522.1) it also experiences this issue.
