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. 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
