I have the same issue, I believe we’d have to report this via pidgin/sipe development. I had seen this in the past when the Lync
server was not reachable. In my case today, it is DNS resolvable, and reachable.
(13:29:53) sipe: sipe_svc_https_response: code 200
(13:29:53) sipe: get_photo_ab_entry_response: received valid SOAP message from service https://lyncwebint.xxxxx.com/groupexpansion/service.svc/WebTicket_Bearer
(13:29:53) sipe: transport_connect - hostname: lyncwebint.xxxxx.com port: 443
(13:29:53) sipe: using SSL
(13:29:53) dnsquery: Performing DNS lookup for lyncwebint.xxxxxx.com
(13:29:53) sipe: http_conn_close: closing http connection: User initiated
(13:29:53) sipe: transport_input_common: new buffer length 4096
(13:29:53) sipe:
MESSAGE START <<<<<<<<<< HTTP - 2013-10-07T11:29:53.744056Z
HTTP/1.1 200 OK
Content-Type: application/photo
Last-Modified: Mon, 07 Oct 2013 08:53:23 GMT
Accept-Ranges: bytes
ETag: “85cf27ae3ac3ce1:0”
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
Date: Mon, 07 Oct 2013 09:29:59 GMT
Content-Length: 2270
���
MESSAGE END <<<<<<<<<< HTTP - 2013-10-07T11:29:53.744056Z
(13:29:53) util: Writing file /home/sadams/.purple/icons/bed94c76cc1a3d26438913338d06e77c3f5ff7c5.jpg
(13:29:53) sipe: http_conn_close: closing http connection: User initiated
Pidgin 2.10.7 has segfaulted and attempted to dump a core file.
This is a bug in the software and has happened through
no fault of your own.
Please make sure to specify what you were doing at the time
and post the backtrace from the core file. If you do not know
how to get the backtrace, please read the instructions at http://developer.pidgin.im/wiki/GetABacktrace
Aborted