Pidgin

Ticket #249 (new defect)

Opened 3 years ago

Last modified 6 months ago

File transfer fails with ICQ 6.0

Reported by: netswipe Owned by: MarkDoliner
Milestone: Patches welcome Component: libpurple
Version: 2.0 Keywords: icq 6.0 oscar file transfer
Cc: dave1g

Description

Just to let you know:

Since the release of icq 6.0 filetranfers are broken again. I did not found any similar ticket in db.

Regards, netti

Change History

Changed 3 years ago by lschiere

  • owner set to MarkDoliner

Changed 3 years ago by MarkDoliner

  • keywords File transfer fails with ICQ 6.0 added; filetransfer icq removed

Changed 3 years ago by MarkDoliner

  • keywords icq oscar file added; File fails with ICQ removed
  • summary changed from Filetransports to File transfer fails with ICQ 6.0

Changed 3 years ago by lschiere

  • milestone set to 2.0.3

Changed 3 years ago by schoen

File transfer with ICQ 6 users works fine for me in both directions, though the sender (ICQ 6 user) gets some weird error message telling them the file transfer had failed, although it has actually succeeded.

Changed 3 years ago by seanegan

  • milestone changed from 2.0.3 to 2.1.0

Milestone 2.0.3 deleted

Changed 3 years ago by MarkDoliner

  • status changed from new to closed
  • resolution set to fixed

I can't reproduce this bug. File transfer works perfectly for me between Pidgin and ICQ 6.0. It's possible it was buggy in Pidgin 2.1.1. I'm using the current code in the repository, which has a few file transfer bug fixes (like the issue schoen mentinoed about the failed message).

Please try again with Pidgin 2.2.0 after it's released (in maybe a week?), and if you're still having problems then please let us know. Thanks!

Changed 3 years ago by schmatzler

File Transfer still doesn't work with some partners, I tried to reproduce the error and it seems, that its sometimes working with ICQ 6 and sometimes not, 5.1 works perfectly (except the error message).

Changed 3 years ago by MarkDoliner

Can you copy and paste the log from the Debug Window from a failed file transfer session?

Changed 3 years ago by schmatzler 

(13:32:01) oscar: Calculating checksum of /home/schmatzler/Desktop/test.jpg
(13:32:01) oscar: Checksum of /home/schmatzler/Desktop/test.jpg calculated
(13:32:01) network: Listening on port: 5190
(13:32:01) network: Couldn't create UPnP mapping
(13:32:01) network: Couldn't create UPnP mapping
(13:32:01) stun: using server 
(13:32:01) oscar: Sent message to 408910146.
(13:32:06) buddyicon: Wrote cache file: /home/schmatzler/.purple/icons/5578f68b79c3b60b5d24b20cf0784654a5bda6e7.jpg
(13:32:06) oscar: Claiming to have a buddy icon
(13:32:06) oscar: Sending IM, charset=0x0000, charsubset=0x0000, length=18
(13:32:06) oscar: Sent message to 40891xxxx.
(13:32:06) msn: S: NS 000: CHL 0 60881029131952172892
(13:32:06) msn: C: NS 000: QRY 11 PROD0038W!61ZTF9 32
(13:32:06) msn: S: NS 000: QRY 11
(13:32:07) msn: C: NS 000: PNG
(13:32:08) msn: S: NS 000: QNG 45
(13:32:16) oscar: Incoming rendezvous message of type 32, user 40891xxxx, status 0
(13:32:16) oscar: Remote user wants to try a different connection method
(13:32:16) dns: DNS query for '87.188.245.227' queued
(13:32:16) dns: Created new DNS child 13184, there are now 1 children.
(13:32:16) dns: Successfully sent DNS request to child 13184
(13:32:16) dns: Got response for '87.188.245.227'
(13:32:16) dnsquery: IP resolved for 87.188.245.227
(13:32:16) proxy: Attempting connection to 87.188.245.227
(13:32:16) proxy: Connecting to 87.188.245.227:1746 with no proxy
(13:32:16) proxy: Connection in progress
(13:32:16) proxy: Connected to 87.188.245.227:1746.

Thats all what I got. Maybe it has to do something with the "different connection method", but I don't know. With Gaim it is working perfectly...

Changed 3 years ago by MarkDoliner

  • status changed from closed to reopened
  • resolution fixed deleted

Changed 3 years ago by MarkDoliner

#3184 is possibly a duplicate of this

Changed 3 years ago by netswipe

Had a file transfer a view minutes ago to a icq 6 user. He sent me a picture of 2 mb. at 48% the transfer froze (for me), nothing was sent anymore. Icq 6 told my friend, that I had stopped the transfer.

Changed 3 years ago by Robby

File transfers with ICQ work fine for me in Adium. If this is still a problem, though, this ticket should get a proper milestone.

Changed 2 years ago by Sim-on

  • milestone changed from 2.2.0 to 2.4.1

Changed 2 years ago by Robby

Hey Sim-on, thanks for milestoning this! :) Can I contact you somehow? I work on Adium's Trac and I see you're very active here, so I think it would be useful if we could exchange information.

Changed 2 years ago by Sim-on

irc.freenode.net
#pidgin

Changed 22 months ago by Halan

this is milestoned for 2.4.1. But i am using 2.5.2 and still have this issue. I can receive but not send files.

Changed 19 months ago by benste

I know it's not very helpful for you, but I filed a bug on launchpad last week, including a log file. I hope someone will take care on this :-)

https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/321548

Changed 19 months ago by Halan

I get something like this on sending: 

(15:45:22) oscar: Sent message to 213421183.
(15:45:28) oscar: Incoming rendezvous message of type 32, user 213421183, status 0
(15:45:28) oscar: Remote user wants to try a different connection method
(15:45:28) oscar: Outgoing peer proxy frame with type=0x0004, unknown=0x00000000, flags=0x0000, and payload length=40
(15:45:28) oscar: Incoming peer proxy frame with type=0x0005, unknown=0x00000000, flags=0x0220, and payload length=0
(15:45:28) oscar: rate change (param ID 0x0001): curavg = 5474, maxavg = 6000, alert at 2000, clear warning at 2500, limit at 1500, disconnect at 800 (window size = 80)

Changed 18 months ago by rekkanoryo

Ticket #3184 has been marked as a duplicate of this ticket.

Changed 18 months ago by rekkanoryo

Ticket #643 has been marked as a duplicate of this ticket.

Changed 18 months ago by rekkanoryo

  • status changed from new to pending

There have been a number of ICQ changes recently. Try Pidgin 2.5.5 and see if the problem persists. Also keep in mind that file transfers may not always work when one or both parties are behind a firewall.

Changed 18 months ago by Halan

I just updated from 2.5.4 to 2.5.5 on ubuntu jaunty and the situation didn't change sadly.

Changed 18 months ago by rekkanoryo

  • status changed from pending to new

Changed 17 months ago by Hanky

File Transfer generelly works fine for me with single files. But if the partner send more than 1 file (it is possilbe with normal ICQ to send multiple files at once) there is no file-name in the popup window, only the file size. So I have to think of an name how the file could be named to save it. The first file is sent correct, but then the filetransfer freeze and I have to abort it. Also see problem here: http://forum.ubuntuusers.de/topic/mehrere-dateien-mit-pidgin-senden-empfangen/ (german)

Reproduce: Start ICQ 6 and open the chat-window to the pidgin user. Open the File Sent Dialog (menu above) and select more than one file. The Pidgin user will have the problems described above.

Changed 17 months ago by Robby

Yes, I believe Pidgin doesn't support ICQ folder transfers but that shouldn't be a major problem. Just compress the folder as a .rar or .zip and send that.

Changed 17 months ago by rekkanoryo

We don't have support for multiple transfers. Someone who wants the feature will have to implement it.

Changed 14 months ago by bernmeister

Should this be moved to Patches Welcome?

Changed 14 months ago by rekkanoryo

  • milestone set to Patches welcome

Sure. If someone can figure out the issue and fix it, I'll gladly apply the patch.

Changed 12 months ago by Hanky

There is a patch from tinloaf!

http://developer.pidgin.im/ticket/365

The author says that the patch is working, but he guess that ICQ 6 is not supported ...

Changed 10 months ago by Halan

It seems to work now on 2.6.3 for me!

Changed 6 months ago by Robby

Ticket #10692 has been marked as a duplicate of this ticket.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!