librepods-org / librepods-org/librepods
[Linux] AppImage crashes on Fedora Wayland
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Environment
- OS: Fedora 43
- GPU: NVIDIA
- LibrePods version: AppImage [linux-v0.1.0]
- Display server: Wayland
What happened
LibrePods crashes immediately on startup with a wgpu panic.
Steps to reproduce
- Launch LibrePods on Wayland
- App crashes instantly
Crash output
[destroyed object]: error 7: importing the supplied dmabufs failed
Protocol error 7 on object @0:
[2026-03-11T17:00:59Z ERROR wgpu_hal::vulkan::adapter] get_physical_device_surface_present_modes: ERROR_SURFACE_LOST_KHR
[2026-03-11T17:00:59Z ERROR wgpu_hal::vulkan::adapter] get_physical_device_surface_formats: ERROR_SURFACE_LOST_KHR
thread 'main' (41262) panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wgpu-core-0.19.4/src/device/global.rs:1859:21:
internal error: entered unreachable code: Fallback system failed to choose present mode. This is a bug. Mode: AutoVsync, Options: []
Workaround
Launching with WGPU_BACKEND=gl prevents the crash.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the AppImage crash on Fedora 43 with NVIDIA under Wayland, using the launch steps and captured wgpu output. Compare startup behavior with WGPU_BACKEND=gl, then trace the startup path involved in surface presentation; done means the AppImage no longer crashes on the reported environment without relying on that workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100