-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug(exec): unable to run program #599
Comments
Thanks for the explanation and try-out, theskpaul. 🙂 |
I had same problem in Windows 11, with an It does need remote SSL inquires validation to checksum? because i got problem with openssl SSL validation |
I have the exact same issue OS: Fedora 40 Silverblue
this is from
I ran it using the iGPU and then dGPU (just in case) (edit) forgot to add vulkaninfo, Silverblue comes with vulkan by default here's Open
|
This comment was marked as off-topic.
This comment was marked as off-topic.
Could this be related to the back-end that |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Uuum.. I'm having this problem as well. `2024-09-13 22:50:37 WARN [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/gles/adapter.rs:774] Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears. internal error: entered unreachable code: Fallback system failed to choose present mode. This is a bug. Mode: AutoVsync, Options: []Protocol error I'm on: Operating System: Solus 4.5 |
Maybe: |
Hmm, I see that users say that it works with |
related #556 |
We should try:
|
I have the same issue on arch linux. This is the log:
|
Describe the bug
Download the latest version, then run it.
the message i get after i run it
Expected behavior
to run
You have a solution?
No response
Operating System
Linux
Window Manager
Wayland
Desktop Environment
GNOME 46.4,
fedora 40,
rustc: 1.81.0 (eeb90cda1 2024-09-04),
cargo: 1.81.0 (2dbb1af80 2024-08-20),
rust-analyzer: 2024-09-09
Provide logs
Acknowledgements
The text was updated successfully, but these errors were encountered: