#1050590 liferea: Having plugin Webkit Setting enabled crashes on startup "libsoup2 and libsoup3 in the same process"

Package:
liferea
Source:
liferea
Description:
feed/news/podcast client with plugin support
Submitter:
Martin Bergström
Date:
2023-10-19 17:36:09 UTC
Severity:
normal
Tags:
#1050590#5
Date:
2023-08-26 17:38:13 UTC
From:
To:
Also crashes immediatly if the Webkit Setting plugin is enabled in UI after startup.

Workaround: Install 1.14.4-3 and disable Webkit Setting plugin then upgrade to 1.15.1-2

Outputs:

Severity important because inexperinced users would have a difficult time discovering
what is wrong, and can not simply turn off the plugin in the UI since the application
does not start. Downgrading the package just to do this could be considered advanced.

#1050590#10
Date:
2023-08-26 18:23:08 UTC
From:
To:
Hi Martin,

Thanks for reporting issues you're experiencing.

For me it even hang my computer, I could move the mouse, but nothing was
responding anymore.

I'll report this upstream and hope they can help to figure out how to
prevent this.

Paul

#1050590#21
Date:
2023-09-21 09:05:38 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
liferea, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1050590@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Gevers <elbrus@debian.org> (supplier of updated liferea package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 21 Sep 2023 10:12:02 +0200
Source: liferea
Architecture: source
Version: 1.15.3-1
Distribution: unstable
Urgency: medium
Maintainer: Paul Gevers <elbrus@debian.org>
Changed-By: Paul Gevers <elbrus@debian.org>
Closes: 1050590
Changes:
 liferea (1.15.3-1) unstable; urgency=medium
 .
   * New upstream version 1.15.3 (Closes: #1050590)
Checksums-Sha1:
 df3e2409480ec13ac4362af4cae79ce1b8aaf3e8 2158 liferea_1.15.3-1.dsc
 875e31506aecbc5bbf4958d86966300f4f8aa439 1861000 liferea_1.15.3.orig.tar.gz
 864432efe6cd6360d6f96086c2a3e65d92e83522 31404 liferea_1.15.3-1.debian.tar.xz
Checksums-Sha256:
 32ba31aae70572c2ce72a629a684d486e9a649c5ab728f516f637ceb7f530620 2158 liferea_1.15.3-1.dsc
 9291f79835ebd2e97b1e126436687ab72a367f768effe7430bbf300dcd2e5d8a 1861000 liferea_1.15.3.orig.tar.gz
 a0ad782604ddf4bfc981e5ceb77a37c6e464c219e688154071a76231a2e61c8b 31404 liferea_1.15.3-1.debian.tar.xz
Files:
 503d2fd42c3a6a4c24cbb2e5afe5686c 2158 web optional liferea_1.15.3-1.dsc
 c39bc8ba52df0949ae398ab36c7c09f1 1861000 web optional liferea_1.15.3.orig.tar.gz
 907e09ac6102a75a7b9e104a2f37d24d 31404 web optional liferea_1.15.3-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmUMBNUACgkQnFyZ6wW9
dQoCgAf+NR4/SItvYq4Yg/NfVwWTCmpie5o/9ZLgONduQ/vVEvQ5E2SWjkYdAopt
7KGJwHLP5RbcEHhQGU5apBEvJrCVPSurYmSibmpabmDxyJSCl1CV8ndFlKFkyIXa
lH+gIIRp8sjMIbrI52YiX4IE7hHc3KkdwoeDMYyF/mYRhG35HN2WwZm9LBoxTOjl
AN8rMcz4RWoMrp3UMKOjfxW1loOekyt4alHNQ4cTRONEaPqYC49sbZY4ePj9pQrw
kZO5GPXE2qBU2suB/IqzV9jiQ79LER6S50RZYn33YwSITqp6xoHID9POeSUmy2yj
pkqpgtYkF6ZDonAI6At867f1yWA5MQ==
=xk7p
-----END PGP SIGNATURE-----

#1050590#26
Date:
2023-09-21 21:15:37 UTC
From:
To:
Sorry, trying 1.15.3-1 the bug persists.

Reading the upstream bug report I expected the application to crash if I
activated the plugin, so that's fine.

However I also expected to be able to launch the application again with
the plugin automatically disabled on startup. This is not the case, the
application still crashes just as before.

/Martin

P.S. Sorry to anyone receiving these emails at martin-at-bredband.net,
my ~/.reportbugrc was misconfigured when I filed the report.

#1050590#31
Date:
2023-09-23 14:08:45 UTC
From:
To:
Hi Martin,

Confirmed. I have asked upstream to reopen the bug report.

Paul