Bug 32752

Created attachment 14274 [details]
Error window of gajim

The error window that pops up, whatever I do with Gajim

CC: (none) => mageia

Try run in terminal and attach in a file the messages, in your screenshot not all the message is there

Hi;

When I launch it from terminal, the error windows do not show up, so I try to log into my account, but it keeps saying connecting and nothing happens.

Here is all that comes out in the terminal:


No translations found for en_US
Dirs searched: [PosixPath('/home/psuave/.local/share'), PosixPath('/home/psuave/.local/share/flatpak/exports/share'), PosixPath('/var/lib/flatpak/exports/share'), PosixPath('/usr/local/share'), PosixPath('/usr/share')]
No plugin translation path available
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 452, in _on_finished
    self._set_complete()
  File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 470, in _set_complete
    self._close_all_streams()
  File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 477, in _close_all_streams
    self._input_stream.close(None)
gi.repository.GLib.GError: g-io-error-quark: Stream has outstanding operation (20)
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 452, in _on_finished
    self._set_complete()
  File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 470, in _set_complete
    self._close_all_streams()
  File "/usr/lib/python3.10/site-packages/nbxmpp/http.py", line 477, in _close_all_streams
    self._input_stream.close(None)
gi.repository.GLib.GError: g-io-error-quark: Stream has outstanding operation (20)
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

Fresh installation in an up to date MGA9 64bit VB Plasma installation:

- starting Gajim via app menu crashes the complete VB guest...

- starting Gajim from terminal (Gajim never opens):
[test@testbox ~]$ gajim
No plugin translation path available

...and the VB guest crashes too after some seconds...

Apparently is a bug in libproxy I found this

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028638#84

That direct me to https://github.com/libproxy/libproxy/issues/199

We need patch libproxy with https://github.com/libproxy/libproxy/issues/199#issuecomment-1397707230 or update to new version where the bug is fixed

Source RPM: gajim-1.6.1-2.mga9.src.rpm => gajim-1.6.1-2.mga9,libproxy-0.4.18-2.mga9

Thank you for this in-depth research.
What radical consequences for sturmvogel comment 4.

The code in question is libproxy/modules/config_envvar.cpp

From the .../199 link:
found libproxy 0.4.15-15 (Debian package) as the last known working version. Seems the issue was introduced by libproxy 0.4.16-1 (Debian package).

A comment Jan 19 (last link above) offers a simple patch.

The comment of Jan 24th shows a different patch that cures the problem; the link shown on Feb 6th shows a full module incorporating the principle of the patch.

From upstream: Library Version: 0.5.3; no date visible; it does not mention anything on this subject.
The threads documenting the error are from only 18/19 Jan, so unless this latest version is more recent - it has to be a patch.

No one packager in view for this SRPM, so assigning globally.

Summary: Gajim keeps crashing => Gajim keeps crashing, fault in libproxy
Assignee: bugsquad => pkg-bugs

(In reply to Lewis Smith from comment #6)
> Thank you for this in-depth research.
> What radical consequences for sturmvogel comment 4.
> 
> The code in question is libproxy/modules/config_envvar.cpp
> 
> From the .../199 link:
> found libproxy 0.4.15-15 (Debian package) as the last known working version.
> Seems the issue was introduced by libproxy 0.4.16-1 (Debian package).
> 
> A comment Jan 19 (last link above) offers a simple patch.
> 
> The comment of Jan 24th shows a different patch that cures the problem; the
> link shown on Feb 6th shows a full module incorporating the principle of the
> patch.
> 
> From upstream: Library Version: 0.5.3; no date visible; it does not mention
> anything on this subject.
> The threads documenting the error are from only 18/19 Jan, so unless this
> latest version is more recent - it has to be a patch.
> 
> No one packager in view for this SRPM, so assigning globally.

Version 0.5.3 is for Jul 7, 2023 , in https://github.com/home-assistant/core/issues/93721#issuecomment-1567162838 say any version higher than 0.4.18 should not have the bug