Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9851 - Pidgin: File Transfer

Attached to Project: Arch Linux
Opened by James (xPlozion) - Sunday, 16 March 2008, 23:28 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 25 March 2008, 12:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Tried to send a file to a friend, he gets a warning on aim saying that i can find out his ip address when i send him a file, he presses the close button then pidgin crashes

Additional info:
pidgin 2.4.0-1


Steps to reproduce:
Send a file to a friend using AIM, then once the transfer is about to initiate, Pidgin will crash... has happened repeatedly to me...

GDB Backtrace:
#0 0xb6e8bbca in snachandler () from /usr/lib/purple-2/liboscar.so.0
No symbol table info available.
#1 0xb6e96a71 in flap_connection_recv_cb ()
from /usr/lib/purple-2/liboscar.so.0
No symbol table info available.
#2 0x080a5505 in ?? ()
No symbol table info available.
#3 0x0873abb8 in ?? ()
No symbol table info available.
#4 0x0000000a in ?? ()
No symbol table info available.
#5 0x00000001 in ?? ()
No symbol table info available.
#6 0xb76dd1fc in ?? () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#7 0x0870a3a8 in ?? ()
No symbol table info available.
#8 0x080a54c0 in ?? ()
No symbol table info available.
#9 0xbffc84d8 in ?? ()
No symbol table info available.
#10 0xb769c89d in g_io_unix_dispatch () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
This task depends upon

Closed by  Dan McGee (toofishes)
Tuesday, 25 March 2008, 12:54 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Upstream issue
Comment by James (xPlozion) - Sunday, 16 March 2008, 23:33 GMT
Got this while running `pidgin -d' in terminal

(19:29:56) util: parsed 266
(19:29:56) upnp: Successfully completed port mapping operation
(19:29:56) stun: using server
(19:29:56) oscar: Sent message to **********.
(19:30:08) oscar: Incoming rendezvous message of type 32, user **********, status 0
(19:30:08) oscar: Remote user wants to try a different connection method
(19:30:08) dns: DNS query for 'ars.oscar.aol.com' queued
(19:30:08) dns: Created new DNS child 14377, there are now 1 children.
(19:30:08) dns: Successfully sent DNS request to child 14377
(19:30:08) dns: Got response for 'ars.oscar.aol.com'
(19:30:08) dnsquery: IP resolved for ars.oscar.aol.com
(19:30:08) proxy: Attempting connection to 205.188.210.217
(19:30:08) proxy: Connecting to ars.oscar.aol.com:5190 with no proxy
(19:30:08) proxy: Connection in progress
(19:30:08) proxy: Connected to ars.oscar.aol.com:5190.
(19:30:08) oscar: Outgoing peer proxy frame with type=0x0002, unknown=0x00000000, flags=0x0000, and payload length=43
(19:30:08) oscar: Incoming peer proxy frame with type=0x0003, unknown=0x00000000, flags=0x0220, and payload length=6
(19:30:08) oscar: Sent message to **********.
Pidgin 2.4.0 has segfaulted and attempted to dump a core file.
This is a bug in the software and has happened through
no fault of your own.
Comment by Dan McGee (toofishes) - Monday, 17 March 2008, 12:52 GMT
I think you really need to report this upstream rather than here.

http://developer.pidgin.im/

Loading...