A WebKitGTK blank window I ran into while building a Tauri 2 update manager #16459
franckagenticdev-stack
started this conversation in
Show and tell
Replies: 1 comment
|
Tauri 2 on Linux — New developer guides available (EN/FR) I've expanded my open-source Tauri 2 / Linux / WebKitGTK troubleshooting playbook with 8 new bilingual guides covering four practical topics:
These guides build on a documented Linux development case involving Zorin OS, Tauri 2, Rust and WebKitGTK. The emphasis is on reproducible observations — not universal fixes or unsupported security claims. The documentation is available in English and French under the MIT license. Repository: Feedback, reproducible reports and contributions are welcome! #Tauri #Rust #Linux #WebKitGTK #OpenSource |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I'm currently building a desktop Update Manager for a larger project I'm working on, using Tauri 2, Rust, React, TypeScript and Vite on Linux.
While getting the desktop side running, I ran into a rather frustrating issue: everything looked fine in the browser, but the native Tauri window was completely white. I also noticed unusually high CPU usage from a WebKitGTK process.
What made this tricky was that the React frontend itself was working. So I started looking more closely at the native runtime and its environment.
One thing that made a difference was launching the app with a fresh, isolated
XDG_CACHE_HOME.The window started rendering again. I then tried a persistent cache directory dedicated to the application, and that worked too. I didn't need to delete or modify my normal user cache.
I also ran into a separate detail worth mentioning: after using
tauri dev, the debug executable I was testing expected the Vite server to be available at127.0.0.1:5173. Rebuilding withtauri build --debug --no-bundlegave me a working standalone debug executable again.These tests were done on Zorin OS 18.1 (Ubuntu 24.04 base).
I haven't established the exact root cause of the original WebKitGTK issue, so I'm treating the isolated-cache approach as a workaround that worked on my machine, not a general fix.
Since I had already spent time investigating it, I decided to put together a small public troubleshooting playbook with the steps, observations and a Bash launcher example.
Here's the repository if anyone finds it useful:
https://github.com/franckagenticdev-stack/tauri2-linux-webkitgtk-playbook
I'd be interested to know if anyone else has encountered similar behavior, especially on Ubuntu-based distributions. Did changing the XDG cache location make any difference for you, or did you trace the blank window to something else entirely?
Any technical feedback is welcome. I'm still learning a few of the subtleties of Tauri and WebKitGTK on Linux, and I'd be happy to improve the documentation based on other developers' experiences.
All reactions