-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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][v2][linux] fails to run on Fedora 40 tauri appimage built on GitHub Actions #10749
Comments
vrc-get/vrc-get#1405 (comment)
Original reporter is using Wayland |
It works on my Fedora system (a real one, not a VM) too but the error somewhat sounds like something nvidia specific which i can't test. Can you ask your users to run the app with the |
Original reporter here! The system where I was having the issue does indeed have an nvidia GPU. I've just tried running the Tauri simple app on a laptop without an nvidia GPU also running Fedora 40 and the application indeed works. I'll try those env variables on my other system with the nvidia GPU and report back once I get home in a few hours. |
Running the application using the |
Okay that's good i guess. It also means that this issue isn't really in our hands though :/ (as long as we keep using webkitgtk). |
Is there anything I can do for improving this problem? |
You could use std::env::set_var to set said env var for every user of your app. Of course that reduces performance for those where the renderer does work fine. Alternatively, we can only wait for new webkitgtk releases. They are actively working on the renderer (which at the same time is the reason why webkitgtk broke for so many people in the first place). |
I thought "as long as we keep using webkitgtk" means it's not fixable due to architecture or something hard to fix in webkitgtk. |
Describe the bug
fails to run on Fedora 40 tauri appimage built on GitHub Actions.
in console output, those log are shown
Downstream issue: vrc-get/vrc-get#1405
Reproduction
Expected behavior
No response
Full
tauri info
outputStack trace
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: