Dear Maintainer,

Updating libwebkit2gtk-4.0-37 beyond 2.44.2-1~deb11u1 (from Debian repo), for
example to 2.48.5-1~deb11u1 (Debian Security repo), renders Gnome Online
Accounts unusable as any invokation ends up showing error: "Webkit encountered
an internal error".

The following error is printed if I run from console "gnome-control-center
online-accounts":

WebKitNetworkProcess: /build/libproxy-
cqqv9A/libproxy-0.4.17/libmodman/module_manager.hpp:58: std::vector<T*>
libmodman::module_manager::get_extensions() const [with T =
libproxy::network_extension]: Assertion `obj != NULL' failed.
ERROR: WebKit encountered an internal error. This is a WebKit bug.

Downgrading libwebkit2gtk-4.0-37 back to 2.44.2-1~deb11u1 resolves the problem.

Gnome Online Accounts (GOA) is being used for GMail.

How to reproduce:
  - upgrade libwebkit2gtk-4.0-37 to the version from Debian Security repo (for
example 2.48.5-1~deb11u1)
  - run "gnome-control-center online-accounts"
  - choose Add account / Google
  - get error described errors in WebKit window and in console
  - downgrade libwebkit2gtk-4.0-37 to the version from Debian repo
(2.44.2-1~deb11u1) and repeat this steps to see there is no error

   * What led up to the situation?

Update of the package libwebkit2gtk-4.0-37 to the version from Debian Security

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Several months ago I updated libwebkit2gtk-4.0-37 to the version from Debian
Security and noticed GOA stopped working. Tracked down to this package and it's
dependencies. Reverting to 2.44.2-1~deb11u1 from Debian repo solves the
problem. Since then I tried updating 2 more times with the same result.

   * What was the outcome of this action?

Version from Debian repo works fine.
Versions from Debain Security don't work.

   * What outcome did you expect instead?

Working Gnome Online Account with any version of libwebkit2gtk-4.0-37 available
from Debian and Debian Security repos.

*** End of the template - remove these template lines ***

Same as #1101807 in atril, but your bug report is much better.

Two additional questions:
1. Do you have an HTTP proxy configured?
2. If yes, using PAC (proxy auto-config)?

I am asking since my guess is that the new WebKitGTK broke
libproxy1-plugin-webkit, which is used for parsing PAC files.

cu
Adrian

В Ср, 27/08/2025 в 20:30 +0300, Adrian Bunk пишет:

Thanks for quick response.

No HTTP proxy used.

I found out a simpler reproduction, it is to just run WebKit example
browser: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser

And, I tested problem with Atril print dialog. First with downgraded
package and it worked fine, then upgraded and Atril crashes ~ one
second after opening print dialog.

That was helpful.

Please check if you have libproxy1-plugin-networkmanager
installed, and whether removing it fixes the issue.

cu
Adrian

В Чт, 28/08/2025 в 12:59 +0300, Adrian Bunk пишет:

It was installed. Removing it fixes the issue.

Emilio, I can reproduce this in bookworm by compiling webkit2gtk with
libc++-16 there.


Plan A would be that someone (not me) debugs what is going wrong in
libproxy when libc++-16 is linked.

libproxy in trixie is a complete rewrite in C, which makes upstream
support for fixing unlikely.


Plan B would be
  Package: libwebkit2gtk-4.0-37
  Breaks: libproxy1-plugin-networkmanager

This would not be nice, but better than runtime breakage.

This would likely also be needed in bookworm if we ever need libc++ there.


cu
Adrian

Hi,

Were you able to reproduce this on bullseye? I am trying to, by installing
libproxy1-plugin-networkmanager, setting a proxy in NM (via PAC file or URL),
but I can't get MiniBrowser to crash.

Cheers,
Emilio

$ /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser
WebKitNetworkProcess: /build/libproxy-cqqv9A/libproxy-0.4.17/libmodman/module_manager.hpp:58: std::vector<T*> libmodman::module_manager::get_extensions() const [with T = libproxy::network_extension]: Assertion `obj != NULL' failed.
ERROR: WebKit encountered an internal error. This is a WebKit bug.
../Source/WebKit/WebProcess/Network/WebLoaderStrategy.cpp(577) : internallyFailedLoadTimerFired

No proxy setting required.

MiniBrowser itself does not crash.

Does it show you a webpage or "WebKit encountered an internal error"?

cu
Adrian

With no proxy set, it shows me webkitgtk.org, and I can navigate just fine (e.g.
go to the planet.webkitgtk.org link, or enter https://google.com).

Cheers,
Emilio

Hi,

Same here.

Also for the previous atril report #1101807, my base bullseye VM has
libproxy1-plugin-networkmanager installed as a dependency of package
'gnome', so it already was installed when I attempted to reproduce the
issue there.

Hence some additional condition seems required to trigger the issue.

Cheers!
Sylvain

I have prepared a backport of webkit 2.50.1 to bullseye. Adrian, can you try it
out and see if that still crashes? Or if you have any further input on how to
reproduce the crash I'd try with 2.48 (and then with 2.50). Binaries are
available from [1].

Cheers,
Emilio

[1] https://debusine.debian.net/debian/developers/work-request/232548/#output

Still reproduces for me.

One thing I noticed is that the crash in MiniBrowser does not happen in
100% of all cases, the problem might be some corruption that manifests
in different ways.

I am always getting the
  ERROR: WebKit encountered an internal error. This is a WebKit bug.
in the terminal where I started MiniBrowser.

cu
Adrian