[GH-ISSUE #325] Error: Wgpu NoSuitableAdapterFound #26

New issue

Closed

opened 2026-03-03 13:45:07 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 13:45:07 +03:00

Owner

Originally created by @rowanfr on GitHub (Mar 12, 2025).
Original GitHub issue: https://github.com/gopher64/gopher64/issues/325

When using the flatpak and running /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=gopher64 io.github.gopher64.gopher64 I get the error output:

thread 'main' panicked at src/main.rs:211:10:
called `Result::unwrap()` on an `Err` value: Wgpu(NoSuitableAdapterFound("`request_adapters` returned `None`"))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I believe I have vulkan available so I should have an adapter. I'm not certain if this is caused by it being a flatpak, or some specific WGPU problem.

Originally created by @rowanfr on GitHub (Mar 12, 2025). Original GitHub issue: https://github.com/gopher64/gopher64/issues/325 When using the flatpak and running `/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=gopher64 io.github.gopher64.gopher64` I get the error output: ``` thread 'main' panicked at src/main.rs:211:10: called `Result::unwrap()` on an `Err` value: Wgpu(NoSuitableAdapterFound("`request_adapters` returned `None`")) note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` I believe I have vulkan available so I should have an adapter. I'm not certain if this is caused by it being a flatpak, or some specific WGPU problem.

kerem closed this issue

2026-03-03 13:45:07 +03:00

kerem commented

2026-03-03 13:45:08 +03:00

Author

Owner

@loganmc10 commented on GitHub (Mar 13, 2025):

this should be fixed in the latest release (1.0.13), can you do a flatpak update and let me know?

@loganmc10 commented on GitHub (Mar 13, 2025): this should be fixed in the latest release (1.0.13), can you do a `flatpak update` and let me know?

kerem commented

2026-03-03 13:45:08 +03:00

Author

Owner

@rowanfr commented on GitHub (Mar 13, 2025):

It works after the latest release. Thanks for resolving this so quickly, I'm impressed

@rowanfr commented on GitHub (Mar 13, 2025): It works after the latest release. Thanks for resolving this so quickly, I'm impressed