Adium/SIPE in Yosemite - Read Error

for Adium, Pidgin, Miranda and Telepathy IM Framework

Brought to you by: aavelar, stefanb2

#266 Adium/SIPE in Yosemite - Read Error

Milestone: OBSOLETE_(1.18.x)

Status: closed-fixed

Owner: nobody

Labels: None

Category: Adium

Priority: 5

Updated: 2016-04-23

Created: 2014-10-20

Creator: Joe

Private: No

Hello,

I had SIPE 1.18.1 and Adium 1.5.9 and was working correctly with Mavericks. Updated to Yosemite over the weekend and today Adium/SIPE doesn’t work in OSX 10.10.

Updated Adium to 1.5.10 and SIPE to 1.18.4 and still it doesn’t work with Yosemite. I’m getting a "Read Error..". I looked into the FAQ, but the error that is mentioned about SSL_BEAST mitigation seems to be different from the one I’m getting.

I have attached the log as well. Please let me know if I’m missing something.

Best Regards,
Joe.

1 Attachments

2014-10-20.log

Related

Forums: Can't connect to Office 365 (AD FS) with Adium

Discussion

<< < 1 2 (Page 2 of 2)

Joe - 2014-10-27

Oh and the bug from Adium

https://trac.adium.im/ticket/16839#comment:1

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2014-10-27

Your crash logs and the one in the Adium ticket look completely different.

I don't know what to do with the crash log. If I understand it correctly it says that the code crashes at sipe_http_request_response + 35 but beyond that the crash log makes no sense to me. Especially the corresponding output from the debug window is missing, so I don't even know what message is supposed to have caused this crash. I'm afraid I can't help you.

Maybe if you compile SIPE in XCode and run it in there, then you should be able to get a backtrace from the crash.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2014-10-27

Just a wild guess: does the crash go away if you tick "Don't publish my calendar data" on the SIPE account options page?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Joe - 2014-10-28
  
  I have enabled the "Don’t publish my calendar data" and till now Adium has been running without any issues (for the last two hour). Will inform you again if it crashes.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2014-10-28

OK, sounds like you might have found another case where EWS autodiscover triggers a crash. Maybe this one only affects Adium. I already fixed to corner cases in 1.18.3 which affected users with older libxml2/glib2 versions.

I need the debug window output to fix this. Please untick the checkmark, start Adium with the CTRL key and open the debug window. The crash should happen after about a minute (or faster if you use the "Republish Calendar" menu). Please save the contents from the debug window and create a new bug report.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Joe - 2014-10-29
  
  I have logged a new bug with the debug log.
  
  https://sourceforge.net/p/sipe/bugs/270/
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

<< < 1 2 (Page 2 of 2)

Log in to post a comment.