FS#77901 - [python-nbxmpp] broken with libsoup3-3.4.0-1

Attached to Project: Community Packages
Opened by Autumn (autumnontape) - Saturday, 18 March 2023, 21:20 GMT
Last edited by Leonidas Spyropoulos (inglor) - Tuesday, 21 March 2023, 22:42 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Morten Linderud (Foxboron)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When starting gajim after upgrading the libsoup3 package from 3.2.2-1 to 3.4.0-1, it fails to connect to the server and displays three error pop-ups with this backtrace repeated twice:

```
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 463, in _on_finished
self._set_complete()
File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 481, in _set_complete
self._close_all_streams()
File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 488, in _close_all_streams
self._input_stream.close(None)
gi.repository.GLib.GError: g-io-error-quark: Stream has outstanding operation (20)

```

And this backtrace a single time:

```
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 303, in _on_timeout
self.cancel()
File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 175, in cancel
raise ValueError('Session already finished')
ValueError: Session already finished

```

Additional info:
* package versions: gajim 1.7.1-2, python-nbxmpp 4.2.0-1, libsoup3 3.4.0-1
* this bug was reported upstream here: https://dev.gajim.org/gajim/python-nbxmpp/-/issues/139
* it was fixed upstream in this commit: https://dev.gajim.org/gajim/python-nbxmpp/-/commit/45e30be68e80fa21d870d56a49cb1d75ef698f3c

Steps to reproduce:
Start gajim and try to connect to a server.
This task depends upon

Closed by  Leonidas Spyropoulos (inglor)
Tuesday, 21 March 2023, 22:42 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.2.1-1 in repos
Comment by Autumn (autumnontape) - Saturday, 18 March 2023, 21:28 GMT
nbxmpp 4.2.1 has already been released with the commit I linked being the only change from 4.2.0, so updating the python-nbxmpp package to 4.2.1 should fix this.

Loading...