Slackware SBo (the 3rd party system packages) upgraded webkit2gtk to 2.34.4 and with it the webkit2gtk api changed to libwebkit2gtk-4.0 to libwebkit2gtk-4.1. This has the unintended effect that the fancy plugin ceases working and moreover, upon rebuilding claws-mail, configure refuses to build the fancy plugin. One can edit the configure script in order for it to accept the newer libwebkit2gtk, but then compilation fails at the fancy plugin with multiple errors. I request, if possible, that you could enable building the fancy plugin with newer libwebkit2gtk versions. Thanks !
That seems odd, Fedora 35 now has webkit2gtk3-2.34.4-2.fc35 which still contains libwebkit2gtk-4.0.so.37 Not sure how come you have a new API version library when built from the same source tarball. I've just rebuilt claws 4.0.0git409 against the same webkit2gtk-devel-2.34.4-2 and fancy builds fine. I am seeing some abrt reports from the .so file now, but I don't think they are claws related, it shows up as problems with pthread calls but claws doesn't crash. These usually happen when I am looking at html mails.
From Debian unstable: dpkg -s libwebkit2gtk-4.0-37 Package: libwebkit2gtk-4.0-37 Status: install ok installed Priority: optional Section: libs Installed-Size: 58736 Maintainer: Debian WebKit Maintainers <pkg-webkit-maintainers@lists.alioth.debian.org> Architecture: amd64 Multi-Arch: same Source: webkit2gtk Version: 2.34.4-1 claws: 4.0.0git409 Fancy builds fine here so it seems to be a problem related to Slackware.
Hi, it's not related to webkit2gtk 2.34.4 per se. The Slackware package maintainers migrated to libwebkit2gtk-4.1, using gtk3 and libsoup3. I'm asking if claws could let the fancy plugin be built under these specs.
libsoup3 seems to be the problem. Looking at claws it doesn't link against libsoup directly but the fancy plugin does. I suppose the fix is for someone who has a system using libsoup3 to look at what is needed in the fancy plugin code. You've tried allowing a higher libsoup version which wasn't sufficient, so you need someone who knows enough to deal with the code changes for the API change while allowing it to work with the earlier API versions.
(In reply to Brian Morrison from comment #4) This could very well be the case. Hence my report.
(In reply to Eduardo Sanchez from comment #5) Yes, I don't know what is needed but I can say that I don't know which mainstream distros have libsoup3 even as a test package. As yet Fedora does not. Not sure if Slackware is viewed as mainstream these days. It's beyond my knowledge, but perhaps one of the dev team is able to comment.
(In reply to Brian Morrison from comment #6) Well, it's *started* the stream (it's the oldest actively maitained Linux distro) so it should be mainstream enough, lol. Anyway, thanks for the insight. Let's hope we get a good outcome.
libsoup3 is not even available in Debian's experimental branch so I guess Slackware is the only distro providing it and therefore this can only be done by one using Slackware and since, to the best of my knowledge, no one in the development team uses Slackware I guess there is a 0% probability for that to happen.
There wasn't when comment #8 was written, but there is now... https://tracker.debian.org/pkg/libsoup3
this all seems to work pefectly on fedora 38 - libwebkit2gtk-4.1 built against libsoup 3.4.2. It seems it either ceased to be a problem, or the problem cannot be fixed in claws-mail.