Aim file transfers not working

I'm on vista64 and the ports are forwarded. I uploaded the debug. Similar to I've had similar results. I can already receive file transfers, but sending them always results in a claim that the receiver canceled. Exactly why isn't that check box selected by default, maybe until the problem is fixed or soemthing?

Is this still happening on 2. Hopefully the fixes in the two related tickets have clobbered this one As such we are purging all AIM issues as it has been 18 months and we are planning on removing the code from our code base in the near future.

Powered by Trac 1. Trac is being migrated to new services! Opened 14 years ago Closed 3 years ago Last modified 3 years ago.

Again: SSL was enabled in all cases. It's annoying that the pidgin developers keep saying this is fixed when it's clearly not.

I'm running Pidgin 2. To summarize what has been going on This was and is a problem with the AOL servers possibly an unannounced update to the protocol? IIRC, the problem fixed itself after about 4 days. Starting, I believe, within the last week, the problem started occurring again. The problem is intermittent, and often trying to log in multiple times in a row i. Starting a few days ago, the problem has changed so that now only having SSL turned on breaks things.

Revision: 0ed15adeb12c1e57ceaf5bff9b71c8abd Ancestor: fab6eeda6b5d68ff2b3fcfd4f Author: darkrain42 … Date: T Branch: im. You know, I feel really dumb because I looked for a ticket before I posted my own duplicate.

It is Ticket Sorry about the duplicate. I literally just updated to the newest version of Pidgin seconds ago, I'm using both Windows XP Professional and Redhat, but both computers give me the following error message:. I'm not good with computers so I've not attempted to make anything work with it yet. Any ideas on how to get it working again? I've tried all the advice here, and nothing is working for me. I used CLientLogin workaround - and it works - but I would like to know some better solution, but Darkrains post is beyond my understanding What exactly it is, how to install it,?

Started having this problem yesterday on Debian. It would tell me I've been disconnecting too frequently and the account was disabled for 10 minutes. Unchecking "Use clientLogin" got it working again. Just noting that ticket is closely related to this one, but precedes it - very similar problem, but with version 2. As another example of the total randomness of when these settings fail, I sign into two AIM accounts on my machine.

One of them consistently the same one works with SSL enabled and clientLogin disabled. Any reason this ticket should stay open? Powered by Trac 1. Trac is being migrated to new services! Opened 12 years ago Closed 12 years ago Last modified 12 years ago. Log of failed login attempt purple-debug. Oldest first Newest first Threaded. Show comments Show property changes. The workaround worked for me in Vista, so it should probably work for any platform.

Confirm that toggling the setting 'use clientLogin' from on to off seems to "fix" the problem. Further confirmations, "me toos", or "CC me" comments are not useful. However, consistent with what Mark said, using the -tls1 flag does work.

I'm getting the message: "Unable to connect to authentication server: SSL Handshake Failed" Is there a way to get more verbose connection logging? Replying to jlsddmar : I'm getting the message: "Unable to connect to authentication server: SSL Handshake Failed" Is there a way to get more verbose connection logging?

Could you please file a new ticket for this? Changed 12 years ago by walter. Closing this ticket as "worksforme" for lack of a more fitting resolution. Oops, apparently it's re-occurring intermittently today. Changed 12 years ago by DHn Confirm that the workaround toggling use clientLogin fixes bug for Windows 7. I'm attaching a debug log with my AIM name removed. Changed 12 years ago by javaJake.

Changed 12 years ago by Leak. Failed connection attempt to ICQ with clientLogon off. I only noticed this because the latest Ubuntu version is 2. This is a show-stopper, guys. Replying to Leak : I just encountered this problem with Pidgin 2. If not then I'm going to close this. Although they were both recorded during the same time, the actual start of the data file may not match the start of the video. Parrot Drones RaceRender can read the.

VBO file format may also work. PZRacing Use. This is the file you will want to use. For example, the first one recorded on Jan 21, would be LOG files should work directly.

You will need to determine which one corresponds to your video file. The PlayMemories software may create these after importing the video onto your computer, but it might make them hidden files. MOFF files should work directly. Their file names should match that of the associated video. In some cases, you may be able to improve compatibility by manually assigning the data fields on the Input File Configuration screen. Sample time in seconds. The first sample does not have to be zero. This may need to be the first column in the file.

Vehicle position longitude X. Can be feet, meters, or coordinates, as long as it's in decimal notation.