Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#76305 - [gajim] 1.5.2-1 "Using libsoup2 and libsoup3 in the same process is not supported" error on start
Attached to Project:
Community Packages
Opened by Pascal Ernster (hardfalcon) - Wednesday, 26 October 2022, 22:20 GMT
Last edited by Toolybird (Toolybird) - Thursday, 27 October 2022, 06:37 GMT
Opened by Pascal Ernster (hardfalcon) - Wednesday, 26 October 2022, 22:20 GMT
Last edited by Toolybird (Toolybird) - Thursday, 27 October 2022, 06:37 GMT
|
DetailsWhen trying to start gajim 1.5.2-1, I get the following error:
(org.gajim.Gajim:31275): libsoup-ERROR **: 00:12:37.218: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. This is caused by gupnp-igd and gupnp 1.2.0-3, which are built against libsoup3 whilst python-nbxmpp 3.2.4-1 is built against libsoup 2.x. I've been able to solve this issue by rebuilding gajim 1.5.2-1 with the optional gupnp-igd dependency removed from the PKGBUILD and with the following patch applied: https://build.opensuse.org/package/view_file/openSUSE:Factory/gajim/0001-remove-upnp.patch |
This task depends upon
Closed by Toolybird (Toolybird)
Thursday, 27 October 2022, 06:37 GMT
Reason for closing: Fixed
Additional comments about closing: gajim 1.5.2-2
Thursday, 27 October 2022, 06:37 GMT
Reason for closing: Fixed
Additional comments about closing: gajim 1.5.2-2
https://dev.gajim.org/gajim/gajim/-/issues/11183
https://bugzilla.opensuse.org/show_bug.cgi?id=1203676
That's a feature, not a bug.
Thanks for the details and links. It seems neither of the people who tested this update so far (including me) had the optional gupnp-igd package installed, so it worked fine.
Does 1.5.2-2 in [community-testing] fix it for you?