-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
GNOME 42: gnome-online-accounts fails to load any webkit view after upgrade #169201
Comments
Originally reported on Reddit, does not appear to be caused by the WebKitGTK compositing issue. |
Could you try running |
Here you go: |
Hmm, that does not reveal much so perhaps the bubblewrap issue is indeed the cause. I would expect the bwrap error to come from but it should I would guess the issue might be that But I still cannot reproduce that, even though I have Could you also check Also, as a workaround, you might try running |
here's the strace.log in case you're interested in it
I guess this is to be expected with the hacky way we reached this point. So I don't think it counts towards the bug. |
Oops, I meant to suggest |
Looks like the strace.log is still too incomplete and we need to increase |
minimally, here's strace.log with 20k string limit |
I've taken the liberty to test page loads with different providers and it seems google has to be the damn thorn. only google's login page causes the exception, and only when I enter my email and press next. |
Oh, I thought you get stuck on a white page, no buttons at all, hence I was focusing on the bubblewrap. I get the following bubblewrap arguments in fresh GNOME VM but they look about the same as yours: bwrap args
I am out of ideas what else to try. Maybe it would be possible to get webkitgtk developer tools but probably not without changing the g-c-c source code. |
I think webkit getting stuck is just a separate issue: the webpage actually renders, but when that nullptr is hit, the webkit view crashes and gets dropped entirely from the window. |
The
Though I still would not expect it to crash. Could you try enabling debug symbols: environment.enableDebugInfo = true;
environment.systemPackages = with pkgs; [
webkitgtk
glib
gtk3
]; and then running it with |
Roughly same issue here on unstable with Wayland on Intel, and I noticed I get the same
I tried running |
I'm in exactly the same situation as @austinbutler , wayland, intel, same errors.. Does someone know a way to connect Gnome to a Google account some other way in the meantime? like forcing to use another browser |
@PaulGrandperrin did you try running it with |
@jtojnar I tried and there was no differences. It makes my remember than I wanted to investigate someday why |
Sorry, it should be |
Ok, I tried: set cmd (dirname (dirname (readlink -f (type -p gnome-control-center))))/libexec/gnome-control-center-goa-helper;WEBKIT_DISABLE_COMPOSITING_MODE=1 WEBKIT_FORCE_SANDBOX=0 GST_PLUGIN_SYSTEM_PATH_1_0=(nix eval --raw n#gst_all_1.gstreamer.out)/lib/gstreamer-1.0:(nix eval --raw n#gst_all_1.gst-plugins-good)/lib/gstreamer-1.0 $cmd create-account google wayland:0 (syntax is different because i use fish and flakes) and it still doesn't work... Thanks to the The console shows this:
|
Ugh, we really might need to switch to WPE according to https://bugs.webkit.org/show_bug.cgi?id=238513, not using is not really tested upstream any more. Unfortunately, we have reverted that in #110738. |
I've been having non-stop issues with EGL applications not working on Wayland + Intel HD graphics See: #169792 |
Build with WPE renderer is no longer tested upstream https://bugs.webkit.org/show_bug.cgi?id=238513#c10 and that configuration is extremely buggy since 2.36.0: NixOS#169201 Previously it was disabled in c0d053e.
Build with WPE renderer is no longer tested upstream https://bugs.webkit.org/show_bug.cgi?id=238513#c10 and that configuration is extremely buggy since 2.36.0: #169201 Previously it was disabled in c0d053e.
Build with WPE renderer is no longer tested upstream https://bugs.webkit.org/show_bug.cgi?id=238513#c10 and that configuration is extremely buggy since 2.36.0: #169201 Previously it was disabled in c0d053e. (cherry picked from commit 303f80a)
I'd like to remind the people here that branch-off is scheduled for tomorrow and depending on how good the staging builds progress, we will branch off rather soon. |
|
Is this working on 22.05 or unstable? |
Don't work for me, on 22.05, Xorg with Nvidia Prime sync enabled. EPiphany don't render de webpages, also online accounts. |
It doesn't work for me as well on latest nixos-unstable. |
That should hopefully be fixed by #201219 |
Build with WPE renderer is no longer tested upstream https://bugs.webkit.org/show_bug.cgi?id=238513#c10 and that configuration is extremely buggy since 2.36.0: NixOS#169201 Previously it was disabled in c0d053e. (cherry picked from commit 303f80a)
Build with WPE renderer is no longer tested upstream https://bugs.webkit.org/show_bug.cgi?id=238513#c10 and that configuration is extremely buggy since 2.36.0: NixOS#169201 Previously it was disabled in c0d053e. (cherry picked from commit 303f80a)
Describe the bug
goa will expire google account access tokens and not allow me to re-login after upgrading to 42.
I've tried clearing everything goa-related from config and cache user dirs, to no avail. It keeps loading infinitely.
Running
gnome-control-center online-accounts
from the commandline and then picking the google account outputs thiserror: bwrap: Can't mkdir parents for /run/current-system/sw/share/fonts: No such file or directory
Steps To Reproduce
Steps to reproduce the behavior:
Screenshots
This is how it looks now when I click on google:
Additional context
gnome-shell is running on wayland by default
Since this seems to be touching fonts, here's my fonts config
Notify maintainers
@bobby285271
@hedning
@jtojnar
@dasj19
@maxeaubrey
Metadata
"x86_64-linux"
Linux 5.15.34, NixOS, 22.05 (Quokka), 22.05pre369756.75ad56bdc92
yes
yes
nix-env (Nix) 2.7.0
"nixos"
/nix/var/nix/profiles/per-user/root/channels/nixos
The text was updated successfully, but these errors were encountered: