#1039725 Pidgin crashes when a file transfer begins

Package:
pidgin
Source:
pidgin
Description:
graphical multi-protocol instant messaging client
Submitter:
Date:
2026-07-06 17:45:12 UTC
Severity:
normal
Tags:
#1039725#5
Date:
2023-06-28 17:34:01 UTC
From:
To:
Hello,

some years ago it was possible to transfer files within a pidgin chat.
Then it becomes slower and in Debian 11 it was nearly impossible.
Now after upgrade to Debian 12 it is impossible, because Pidgin crashes
whenever a file transfer begins.

This looks this way in the console:

$ pidgin
Pidgin 2.14.12 hat einen Speicherzugriffsfehler festgestellt und
versucht, eine Core-Datei zu schreiben.  Dies ist ein
Fehler im Programm und kein Fehler von Ihnen.

Wenn Sie den Absturz reproduzieren können, informieren Sie
bitte die Entwickler mit einem Fehlerbericht auf:
https://pidgin.im/development/simpleticket/

Bitte geben Sie unbedingt an, was Sie getan haben als der
Fehler aufgetreten ist, und posten Sie den Backtrace aus
der Core-Datei. Falls Sie nicht wissen, wie man einen
Backtrace erstellt, lesen Sie bitte die Informationen auf
https://pidgin.im/development/wiki/GetABacktrace
Abgebrochen (Speicherabzug geschrieben)

Speicherzugriffsfehler = segmentation fault
There is no dump afterwards.

A start with
gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' -ex
'thread apply all bt full' --args pidgin
only shows at the crash:

Thread 1 (Thread 0x7fb3feadeb00 (LWP 19842) "pidgin"):
#0  0x00007fb3ffcdf324 in purple_xfer_prpl_ready () from
/lib/x86_64-linux-gnu/libpurple.so.0
No symbol table info available.
#1  0x00007fb3fc669636 in jabber_iq_parse () from
/usr/lib/x86_64-linux-gnu/purple-2/libjabber.so.0
No symbol table info available.
#2  0x00007fb3fc67e824 in ?? () from
/usr/lib/x86_64-linux-gnu/purple-2/libjabber.so.0
No symbol table info available.
#3  0x00007fb3fef81bbb in ?? () from /lib/x86_64-linux-gnu/libxml2.so.2
No symbol table info available.
#4  0x00007fb3fef8270b in xmlParseChunk () from
/lib/x86_64-linux-gnu/libxml2.so.2
No symbol table info available.
#5  0x00007fb3fc67ecdd in jabber_parser_process () from
/usr/lib/x86_64-linux-gnu/purple-2/libjabber.so.0
No symbol table info available.
#6  0x00007fb3fc66d7f9 in ?? () from
/usr/lib/x86_64-linux-gnu/purple-2/libjabber.so.0
No symbol table info available.
#7  0x000055f72c71401e in ?? ()
No symbol table info available.
#8  0x00007fb3fff5267f in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#9  0x00007fb3fff52a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#10 0x00007fb3fff52cef in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#11 0x00007fb400536b2a in gtk_main () from
/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
No symbol table info available.
#12 0x000055f72c6d7e55 in main ()
No symbol table info available.

The hope was that the slow speed is fixed now, but it could not be
proved, because it crashes always.

https://issues.imfreedom.org/issue/PIDGIN-17293

This should be fixed in
https://keep.imfreedom.org/pidgin/pidgin/rev/12e26d298873
<https://keep.imfreedom.org/pidgin/pidgin/rev/12e26d298873> and will in
the 2.14.11 release.

Now we have version 2.14.12 and it crashes instead of being slow.

What can be done?

#1039725#12
Date:
2023-07-23 04:16:08 UTC
From:
To:
A few questions that are necessary to figure this out. Was the peer on
the same lan or was this over the internet. Also is ipv6 a possibility
here?

Thanks,