Closed rahlhar closed 1 year ago
Did you use wyebadblock compiled for webkit2gtk-4.1? In my ebuild for it I compile it for 4.1 https://github.com/jjakob/gentoo-overlay/blob/master/www-misc/wyebadblock/wyebadblock-1.0.0_p20230212.ebuild
@jjakob Cheers! This was exactly what I needed.
Turns out I had also poorly read both the README of wyebadblock
and the comments in the AUR.
Altered the PKGBUILD
, recompiled and all is well with the world again.
Much appreciated.
Steps to reproduce
Perhaps:
vimb
wyebadblock
vimb
Not entirely known. Running fine having installed on
artix
, but after installingbadwolf
andwyebadblock
, which I believe pulled inwebkit2gtk
, I get the following error, resulting inwebview
crashing.I've included the whole console output, though I think the initial warnings are unrelated.
I'm using
artix
withwayland
anddwl
as the compositor.xwayland
is also installed.Expected behaviour
vimb
to usewbkit2gtk-4.1
even ifwebkit2gtk
is also installed, and forwebview
to run fine.Actual behaviour
vimb
appears to use an older version ofwebkit2gtk
if present, which I believe useslibsoup2
instead oflibsoup3
;webview
crashes.Notes
This felt like it could be related to issue 708, but that was solved with PR 727.
I thought the issue was that
vimb
was not usingwebkit2gtk-4.1
, but while writing this report, I can see it should be - it depends on it and it is installed - but it seems it is not prioritising it over older versions.This looks to be supported by the output from
vimb --bug-info
.