Hi,
On 02/09/2025 11:51, Adrian Bunk wrote:
On Fri, Aug 29, 2025 at 01:30:05AM +0300, Konstantin Pokotilenko wrote:
В Чт, 28/08/2025 в 12:59 +0300, Adrian Bunk пишет:
On Wed, Aug 27, 2025 at 10:08:05PM +0300, Konstantin Pokotilenko
wrote:
В Ср, 27/08/2025 в 20:30 +0300, Adrian Bunk пишет:
...
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.
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
...
That was helpful.
Please check if you have libproxy1-plugin-networkmanager
installed, and whether removing it fixes the issue.
It was installed. Removing it fixes the issue.
Emilio, I can reproduce this in bookworm by compiling webkit2gtk with
libc++-16 there.
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
