Hi, I can confirm this is fixed in Debian Buster with the security update to WebKitGTK 2.26.4:
# dpkg -l | grep webkit2 ii gir1.2-webkit2-4.0:amd64 2.26.4-1~deb10u1 amd64 Web content engine library for GTK - GObject introspection data ii libwebkit2gtk-4.0-37:amd64 2.26.4-1~deb10u1 amd64 Web content engine library for GTK ii libwebkit2gtk-4.0-37-gtk2 2.26.4-1~deb10u1 all Transitional dummy package ii libwebkit2gtk-4.0-dev:amd64 2.26.4-1~deb10u1 amd64 Web content engine library for GTK - development files ii libwebkit2gtk-4.0-doc 2.26.4-1~deb10u1 all Web content engine library for GTK - documentation Thanks to all parts involved in fixing this, particularly to Carlos Garcia Campos for providing the fix and Alberto Garcia for bringing WebKitGTK 2.26.4 into buster-security! ☺ On Tue, 18 Feb 2020 00:11:04 +0100 Alberto Garcia <be...@igalia.com> wrote: > On Wed, Jan 29, 2020 at 12:22:04PM +0100, Alberto Garcia wrote: > > > > For WebKit, let's discuss in > > > https://bugs.webkit.org/show_bug.cgi?id=202194 to keep things in one > > > place. > > > > So there's now a patch for the WebKit 2.26 branch that IIUC would > > solve this problem without having to patch Evolution at all. > > > > https://trac.webkit.org/changeset/255350/webkit > > > > If everything works fine it will be available in the next stable > > release of the webkit2gtk package. > > WebKitGTK 2.26.4 is now available in testing, sid and buster-security, > can anyone check if that fixes this problem in Evolution? > > Thanks! > > Berto > > -- Br, Andres
signature.asc
Description: This is a digitally signed message part
