-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Blank window #2977
Comments
Same issue for every Wails project (with this Archlinux config). Not just for a new created project. |
I wonder if your systems silently upgraded some deps. There's no reason anything should change overnight with your code or deps.... |
Have you tried disabling compositing? https://bugs.webkit.org/show_bug.cgi?id=180739 You could also adjust this: https://wails.io/docs/reference/options/#webviewgpupolicy |
|
What will be the permanent fix? |
Standardisation in Linux distros 😅 |
I saw similar issue when open my cisco anyconnect client. so I search the error and I found this. I have a WAR that use |
Thanks for the info. Sounds like an ecosystem wide issue 😞 |
If anyone who is having the issue is comfortable with local Dev, then setting this environment in this function might fix the issue: https://github.com/wailsapp/wails/blob/master/v2/internal/frontend/desktop/linux/frontend.go#L139 If it does we can make it a flag. |
There are several webkit bug reports related to this: This is clearly webkit/nvidia related and there's no real fix yet (even the nv drivers update mentioned in 281874 does not fix this bug for me). IMO, the best way to tackle this in wails and its ecosystem is:
This way, end-users won't even see the bug and this would put less pressure on devs. |
Assuming that very little client code uses the diff --git a/v2/internal/frontend/desktop/linux/window.go b/v2/internal/frontend/desktop/linux/window.go
index 82030f43..71516097 100644
--- a/v2/internal/frontend/desktop/linux/window.go
+++ b/v2/internal/frontend/desktop/linux/window.go
@@ -25,6 +25,7 @@ import (
"github.com/wailsapp/wails/v2/internal/frontend"
"github.com/wailsapp/wails/v2/pkg/menu"
"github.com/wailsapp/wails/v2/pkg/options"
+ "github.com/wailsapp/wails/v2/pkg/options/linux"
)
func gtkBool(input bool) C.gboolean {
@@ -90,6 +91,9 @@ func NewWindow(appoptions *options.App, debug bool, devtoolsEnabled bool) *Windo
var webviewGpuPolicy int
if appoptions.Linux != nil {
webviewGpuPolicy = int(appoptions.Linux.WebviewGpuPolicy)
+ } else {
+ // TODO: see https://github.com/wailsapp/wails/issues/2977
+ webviewGpuPolicy = int(linux.WebviewGpuPolicyNever)
} Then add a warning in the docs for |
Happy to accept a PR on this. Agree - it's probably the best way forward. |
In NewWindow, set options.Linux.WebviewGpuPolicy to WebviewGpuPolicyNever if options.Linux is nil, disabling GPU acceleration by default on linux until the upstream bugs https://bugs.webkit.org/show_bug.cgi?id=228268 and https://bugs.webkit.org/show_bug.cgi?id=261874 are fixed.
In NewWindow, set options.Linux.WebviewGpuPolicy to WebviewGpuPolicyNever if options.Linux is nil, disabling GPU acceleration by default on linux until the upstream bugs https://bugs.webkit.org/show_bug.cgi?id=228268 and https://bugs.webkit.org/show_bug.cgi?id=261874 are fixed.
Here you go #3027. |
In NewWindow, set options.Linux.WebviewGpuPolicy to WebviewGpuPolicyNever if options.Linux is nil, disabling GPU acceleration by default on linux until the upstream bugs https://bugs.webkit.org/show_bug.cgi?id=228268 and https://bugs.webkit.org/show_bug.cgi?id=261874 are fixed.
I ran into this issue trying use webkit2gtk on arch linux (with an nvidia card) and I was able to fix it without setting Here is how I fixed it:
|
Thank you so much @nobane this works perfectly on my Arch machine. |
How long is this going to be a problem? May not be directly your fault but the last Archlinux build of the I have |
Did not work for me but |
@leaanthony this is still happening in V3 alpha. |
Do you know what the solution is? |
Not really. I ended up disabling the renderer. |
I came here just because I got the fatal error "signal handler set by non-Go error" but apprently it is isn't related to this bug altough I have the same message "Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal" when Wails start too. That being said, the But I don't have it on wails from my side. One difference between the two is that wails required me to install
|
Description
Yesterday my app worked just fine. This morning, after making no changes to the code, I executed
wails dev
and it resulted in a full gray window. However when I randomly move my mouse on the window I can see the tooltips of my app.Can't even open the dev tools in the wails window. Works in the browser though (
wails dev --browser
).My
main.go
does correctly include the assets:Wails dev output:
When I try to run the binary after building:
My coworker's output:
To Reproduce
Expected behaviour
I expect a properly working Wails app window
Screenshots
wails dev --browser
Attempted Fixes
Remove webkit packages. Break my system. Cry. Reinstall webkit. Reinstall Gnome. No solution.
System Details
Me:
Kubuntu 22.04
Wails v2.4.1
Vite v3.1.8
Webkit: libwebkit2gtk-4.0-37 libwebkit2gtk-4.0-dev
My co-worker who has the same issue:
Arch Linux (kernel: 6.5.6-arch2-1)
Wails v2.6.0
Webkit: webkit2gtk 2.42.1-1 webkit2gtk-4.1 2.42.1-1 webkitgtk-6.0 2.42.1-1
Additional context
Similar to #2975 and #9
The text was updated successfully, but these errors were encountered: