Page 1 of 1
1.3.2 MSN Error:read error
Posted: Mon Oct 27, 2008 7:27 pm
by myha
Hi,
I cannot connect to MSN at all, I have tried everything but nothing seems to help: Installed the older version of Adium, I completely removed everything under ~/.AppSupport/Adium and entered all logins again but nothing seems to help.
Other accounts are working fine (Facebook and GTalk).
Error is the following:
and the output from system.log:
Code: Select all
[mihap@Hackint0sH ~/Desktop] tail -f /var/log/system.log | grep -i adium
Oct 27 20:25:21 Hackint0sH [0x0-0xa20a2].com.adiumX.adiumX[3227]: Debugger() was called!
Oct 27 20:25:22 Hackint0sH [0x0-0xa20a2].com.adiumX.adiumX[3227]: SocketRead: read(5) error 0
Oct 27 20:25:22 Hackint0sH [0x0-0xa20a2].com.adiumX.adiumX[3227]: SocketRead err = -9802
Any ideas?
Re: 1.3.2 MSN Error:read error
Posted: Mon Oct 27, 2008 8:32 pm
by Simon Patterson
I'm having the same problem... its so annoying not even safari wont connect to live.com
Re: 1.3.2 MSN Error:read error
Posted: Mon Oct 27, 2008 8:44 pm
by myha
yes, very annoying... Is this an Adium thing or what?
Re: 1.3.2 MSN Error:read error
Posted: Mon Oct 27, 2008 8:54 pm
by zac
Since the OP is using illegal hardware/software combinations, I'm not sure I trust his output anyway.
See
http://adiumx.com/faq/ReportingBugs for how to file a bug report and get debug logging.
Re: 1.3.2 MSN Error:read error
Posted: Mon Oct 27, 2008 10:15 pm
by Dimmuxx
This is just a temporary server issue.
Re: 1.3.2 MSN Error:read error
Posted: Tue Oct 28, 2008 1:33 pm
by myha
kinda long temp error since it goes on for at least a week...
Re: 1.3.2 MSN Error:read error
Posted: Wed Oct 29, 2008 7:30 pm
by myha
just tried to login from fresh install of leopard server on vmware and I receive the same error...
Re: 1.3.2 MSN Error:read error
Posted: Thu Oct 30, 2008 7:29 pm
by Simon Patterson
Dimmuxx wrote:This is just a temporary server issue.
I'm not quite sure if the word "temporary" is right to define this problem. temporary would be one day or two. this is to be honest a pain in the ass. I'm glad Adium is not a payware. if so I would be very disapointed to pay for this long development or failure to solve problems
Re: 1.3.2 MSN Error:read error
Posted: Thu Oct 30, 2008 9:04 pm
by alcmaer
Maybe you should complain about this at
http://www.hackint0sh.org/ .
It's not Adium's fault when a good program doesn't work at illegal stuff, is it?
Re: 1.3.2 MSN Error:read error
Posted: Thu Oct 30, 2008 11:03 pm
by Dimmuxx
Simon Patterson wrote:I'm not quite sure if the word "temporary" is right to define this problem. temporary would be one day or two. this is to be honest a pain in the ass. I'm glad Adium is not a payware. if so I would be very disapointed to pay for this long development or failure to solve problems
You said you couldn't browse live.com in safari either so it's a temporary server problem or in your case most likely a network error on your side.
Re: 1.3.2 MSN Error:read error
Posted: Sun Nov 02, 2008 11:50 pm
by Simon Patterson
alcmaer wrote:Maybe you should complain about this at
http://www.hackint0sh.org/ .
It's not Adium's fault when a good program doesn't work at illegal stuff, is it?
u mean refering to previous link that my adium wont work/connect to just msn messenger protocol because of Adobe CS4?
Re: 1.3.2 MSN Error:read error
Posted: Tue Nov 04, 2008 11:47 am
by myha
alcmaer wrote:Maybe you should complain about this at
http://www.hackint0sh.org/ .
It's not Adium's fault when a good program doesn't work at illegal stuff, is it?
KHM... I have MBP early2008. Hackint0sH hostname is from before-mac days. But it doesnt matter at all.
Anyway, the issue was resolved and was not an adium issue - I needed to change country in MSN profile... Why now I have no idea, after 10 years of usage...
Re: 1.3.2 MSN Error:read error
Posted: Tue Nov 04, 2008 7:15 pm
by alcmaer
Zac's remark "Since the OP is using illegal hardware/software combinations..." and the name "
Hackint0sH" made me think it was something illegal.
If I was wrong, I apologize for my posting.
Re: 1.3.2 MSN Error:read error
Posted: Tue Nov 04, 2008 11:16 pm
by zac
myha wrote:KHM... I have MBP early2008. Hackint0sH hostname is from before-mac days. But it doesnt matter at all.
Anyway, the issue was resolved and was not an adium issue - I needed to change country in MSN profile... Why now I have no idea, after 10 years of usage...
Sorry. The number of error reports I see from simply running a hacked version of the OS leads me to jump to conclusions pretty fast at any indication; it's a huge waste of time to get in-depth with a problem only to discover it's because a library is running on completely unsupported hardware and performs unexpected.
Re: 1.3.2 MSN Error:read error
Posted: Wed Nov 05, 2008 8:02 am
by myha
Yes, I can imagine it can be a pain in the ass.
Re: 1.3.2 MSN Error:read error
Posted: Thu Nov 05, 2009 4:16 am
by Spines
Ive been getting the same problem with both MSN and AIM. My web connection is fine at the same time I am getting logged out. Oh and I'm not on a h@cK!nT0sH lol
From my error log:
11/3/09 11:07:05 PM [0x0-0x3a13a1].com.apple.Safari[84238] Debugger() was called!
11/4/09 10:06:02 AM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 10:06:02 AM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 11:05:26 AM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 11:05:26 AM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 1:14:53 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 1:14:53 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 1:34:47 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 1:34:47 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 1:38:31 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 1:38:31 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 1:43:47 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 1:43:47 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 1:46:07 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 1:46:07 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 10:15:06 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 10:15:06 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 10:29:48 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 10:29:48 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 10:33:42 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 10:33:42 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
11/4/09 10:49:20 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 10:49:20 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead: read(5) error 0
11/4/09 10:49:20 PM [0x0-0x2c72c7].com.adiumX.adiumX[57807] SocketRead err = -9802
I just downloaded an update we'll see if that fixes it
EDIT: PS what's with the dude who posted before me having his post dated later than mine?
2nd edit: Because it was today a year ago, I found this thread on a google search and I didnt notice that it was from 2008 lol
3rd Edit: The update seems to have resolved the issue.