abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 23678 bytes cmdline: pidgin component: pidgin Attached file: coredump, 47595520 bytes crash_function: sighandler executable: /usr/bin/pidgin kernel: 2.6.35.12-88.fc14.i686.PAE package: pidgin-2.7.11-1.fc14 rating: 4 reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1303147340 uid: 500 How to reproduce ----- 1. 2. 3. dunno
Created attachment 495974 [details] File: backtrace
Package: pidgin-2.7.11-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.finalizo transferencia de un archivo 2. 3.
Package: pidgin-2.7.11-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open a conversation on msn, OTR plugin enabled 2. Send a File.png 3.Crash when finished Comment ----- I tryed to send a file.png through pidgin When the transfer was completed it crashed BTW, y was typing a message in the meanwhile
Package: pidgin-2.7.11-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Log in on MSN protocol 2. Try to send file over MSN protocol 3. Comment ----- File was quite small 5.7kB. Max transffered only 81%
Package: pidgin-2.7.11-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.sending an archive 2. 3.
Package: pidgin-2.9.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Send a .pdf file with utf-8 characters ( ex. аяюуя.pdf ) 2. Wait until it go to 100% 3. After transaction is done, pidgin crashes.
Package: pidgin-2.10.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Send file via MSN protocol . Near 100% it will crash
Backtrace analysis found this bug to be similar to bug #684518, closing as duplicate. Bugs which were found to be similar to this bug: bug #684518, bug #737289 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 684518 ***