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
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When 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
Comment by Pascal Ernster (hardfalcon) - Wednesday, 26 October 2022, 22:21 GMT Comment by Toolybird (Toolybird) - Thursday, 27 October 2022, 03:28 GMT
@blakkheim, I still can't see you in flyspray's list of folks who can have bugs assigned to them. You should chase this up :)
Comment by T.J. Townsend (blakkheim) - Thursday, 27 October 2022, 04:02 GMT
> I still can't see you in flyspray's list of folks who can have bugs assigned to them.

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?
Comment by Pascal Ernster (hardfalcon) - Thursday, 27 October 2022, 06:28 GMT
Yes, 1.5.2-2 solves the issue. Thank you! :)

Loading...