MSN messages not getting through?

[fueg0]

Updated to 0.73 and it would appear that this MSN bug is still ongoing. What I have noticed now is that following each message I send out, an error message of some sort would come back. But this error message would not be recorded in Adium Log.

Other than that, there's this following message in the Console repeated many many times...

** (process:3315): CRITICAL **: file /Users/evands/libgaim/libgaim/src/protocols/msn/cmdproc.c: line 112 (msn_cmdproc_send_trans): assertion `cmdproc->ready' failed

i manage continue using AdiumX after chating with some members of the Dev. Team !
So, the solutions is: Downgrade to 0.72 and wait a new adium with a good libgaim !

[sogood]

i manage continue using AdiumX after chating with some members of the Dev. Team !
So, the solutions is: Downgrade to 0.72 and wait a new adium with a good libgaim !

I doubt that's a decent solution. 0.72 has the same or similar MSN bug where messages to other MSN users would intermittantly disappear, although 0.73 just has some extra error messages.

Guess it's a case of wait and see...

[fueg0]

i manage continue using AdiumX after chating with some members of the Dev. Team !
So, the solutions is: Downgrade to 0.72 and wait a new adium with a good libgaim !

I doubt that's a decent solution. 0.72 has the same or similar MSN bug where messages to other MSN users would intermittantly disappear, although 0.73 just has some extra error messages.

Guess it's a case of wait and see...

But, believe me, it's a GREAT SOLUTION. You know why? Because this

Code: Select all

22:32:49 wlc98clark: no, the latest stable is .73, but .73 has the newer libgaim that has an MSN bug in it -- .72 has the older libgaim

So, since yesterday that i downgrade from 0.73 to 0.72 and the errors are gone and this adium is STABLE.

I think the new libgaim has a memory leak and tries to do a

Code: Select all

free()

to a memory zone that it's not from libgaim. So, it crashes.
This is only IMHO.

[sogood]

Interesting. 0.73 has not crashed once for me whereas 0.72 has on multiple occasions. I wait...

[evands]

And this is why development is not a cakewalk

[xGrape]

I still have people who are not getting my messages, and I get no errors. Now running Adium 0.74. Where can I check for errors? I couldn't find any in the Console, but I might've been looking in the wrong place...

[dchoby98]

You can filter the console contents for "Adium" (use the search field in the upper right of the window) -- that will at least show only the Adium logs. However, I doubt that you will find much -- but do check!

[Babsi-Mueller]

I'm using 0.75.1 and still have the problem that every now and then a line that my counterpart enters (using the newest MSN for WinXP) doesn't shop up in my window.

I can see the "Your Buddy is typing...." icon but then: nothing, no text. I don't get any error message btw

ahm, and both our connections are rather fast...

I don't know if this is an Adium-bug, but it is quite annoying. I tried the "number every line - trick" to make sure that lines got lost and yes, every 15th or 20th line didn't make it through to me.

Interesting: all of MY lines made it to the other side though

regards

B

[SoopaBanana]

I'm running 0.76 and I still cannot get messages (my friends got so frustrated that we started "chatting" via e-mail...) I'm sooo grateful of AdiumX because it is simply one of the best apps available, but the message problem is killing me!

edit: I'm running MSN from HTTP protocol and systemwide HTTP proxy Would that be a problem?

[evands]

I'm running 0.76 and I still cannot get messages (my friends got so frustrated that we started "chatting" via e-mail...) I'm sooo grateful of AdiumX because it is simply one of the best apps available, but the message problem is killing me!

edit: I'm running MSN from HTTP protocol and systemwide HTTP proxy Would that be a problem?

Hm, the HTTP protocol for MSN was supposed to be fixed in 0.76... it's the most unreliable part of MSN... and proxy support isn't perfect... and HTTP proxy support is the most unreliable proxy type. So you've got a nasty combination there unfortunately

I'll put together a debug build for you (and others in this thread still seeing this problem) and post it here later this week... hopefully some debug output can give us some insight into what's going wrong.