Empty dark gray screen on startup

Question

Empty dark gray screen on startup

Kernald opened this issue 4 years ago · 14 comments

Using 0.4.0 on Linux, I get an empty, dark gray (regular background colour) on startup, and nothing else. Starting from a terminal, I get this (and only this):

Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal

When closing the window, the process exits normally (0).

I didn't find any flag to make it more verbose or anything. It used to work on the same machine a few weeks ago, and can't figure out what might have changed since then. I tried removing ~/.cache/wombat and ~/.local/share/Wombat, it didn't make a difference.

What can I do to get more insights to troubleshoot this?

Answer 1 · 2021-04-08T10:51:03.000Z

Having the same problem with 0.4.0 and 0.3.3 on Arch with Wayland.

Which Linux are you using? Do you use xorg or Wayland?

Answer 2 · 2021-04-08T10:52:10.000Z

Archlinux as well, but Xorg (proprietary nVidia drivers).

Answer 3 · 2021-04-09T10:57:24.000Z

Same problem here since the beginning of April. Arch Linux, KDE, Xorg, nVidia proprietary drivers. Other programs I use doesn't seem to be affected.

Answer 4 · 2021-04-09T11:20:09.000Z

Could this be related to the update of libwebkit2gtk (webkit2gtk 2.32.0-1 pkg) which is used by this project?
See also release notes

Answer 5 · 2021-04-10T01:20:24.000Z

I'm not sure exactly how it's used, so I'm not sure if there's a dependency to upgrade or anything (I'm really not familiar with Go, but I couldn't find any direct reference to webkitgtk), but just rebuilding Wombat doesn't help.

Answer 6 · 2021-04-11T01:39:44.000Z

I believe this is caused by this Wails issue: wailsapp/wails#658 (a recent webkit2gtk update broke it, as speculated). I just opened a PR to update Wails which should fix this.

Answer 7 · 2021-04-11T03:09:43.000Z

Thanks for opening this @aschey. It looks like recent version of gtkwebkit don't expose window.external any more so we have a patch against that now.

Answer 8 · 2021-04-15T13:04:15.000Z

Hey everyone. Can we have some kind of progress info on this one? Wombat is totally broken now, and alternatives are not that good.

Answer 9 · 2021-04-15T16:18:14.000Z

Currently waiting on my PR to be reviewed and merged. In the meantime, you can build from my branch here: https://github.com/aschey/wombat/tree/update-wails-and-go

Answer 10 · 2021-04-16T09:42:52.000Z

same problem here

Answer 11 · 2021-04-23T15:34:29.000Z

Any chance of a release soon? I am stock with gRPC-UI tool for now and eagerly waiting a release of Wombat with this issues fixed.

Answer 12 · 2021-04-24T00:34:15.000Z

@patkoscsaba I'm not sure when the next version will be released so here's a build from the latest master branch that I did on my local machine: https://filebin.net/tqjpph3h7ef580zf

Answer 13 · 2021-04-24T05:59:55.000Z

Sorry for the delay everyone. Just fixing up a few bugs and will get a new release cut soon. 🙏

Answer 14 · 2021-04-24T08:35:33.000Z

@aschey Thanks. That starts up and seems to be working. Even if there are a few bugs, it's better than not having anything.
@rogchap Sure, I am not complaining or pressuring you. After all it is a free and open source project. Take your time. And good job with Wombat. It is by far the best gRPC GUI client out there. I tried all the others while Wombat was not working, and I was disappointed. gRPC UI is decent, and it is cool that you can deploy it along with your server, but without realtime streams it is awkward to be used.