Description of problem: Using pidgin with purple-sipe logged into a Office Communicator system. I can log in using Kerberos (not NTLM), however after sending a message, pidgin disconnects my login. I then have to immediately log back in to pidgin to see any responses. Version-Release number of selected component (if applicable): pidgin-sipe-1.18.0-1.fc20.x86_64 pidgin-2.10.7-8.fc20.x86_64 libpurple-2.10.7-8.fc20.x86_64 purple-sipe-1.18.0-1.fc20.x86_64 openssl-libs-1.0.1e-37.fc20.x86_64 openssl-1.0.1e-37.fc20.x86_64 openssl-libs-1.0.1e-37.fc20.i686 How reproducible: Using an existing Active Directory account, configure Pidgin to connect to an Office Communicator service. Steps to Reproduce: 1. Log in to Pidgin with the OCS account 2. Enter a message to a contact on the list 3. Actual results: Pidgin logs out with the following message in the GUI: username,example.com\username disconnected Write error. Expected results: Message sent, without Pidgin disconnecting user Additional info: This was not an issue with Fedora 19. I have downgraded my openssl packages, along with my sipe packages on the Fedora 20 system, however I can not connect after doing so. This system was just recently upgraded from Fedora 19, where this was not an issue (the Fedora 19 installation was fully updated prior to the upgrade).
Also, changing status using the dropdown at the bottom of the GUI causes the same behavior
Adding an strace of a complete session where Pidgin crashes after sending a message
Created attachment 855101 [details] strace of pidgin crashing strace of pidgin crashing
Here is some output from running pidgin -d: MESSAGE START >>>>>>>>>> SIP - 2014-01-24T18:21:35.080386Z INVITE sip:jmhoch SIP/2.0 Via: SIP/2.0/tls 10.66.60.52:44738 From: <sip:klarmstrong2>;tag=746662575;epid=41d171354cee To: <sip:jmhoch> Max-Forwards: 70 CSeq: 1 INVITE User-Agent: Purple/2.10.7 Sipe/1.18.0 (linux-x86_64; RTC/3.5) Call-ID: 9826gF660aE774iB5F4m4DD3tC057bC674x0E3Ex Supported: ms-sender Contact: <sip:klarmstrong2;opaque=user:epid:_iujKgXGDl2i7ebBXNIEGAAA;gruu> ms-text-format: text/plain; charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AUwAlADIAMABTAGEAbgBzACUAMgAwAFMAZQByAGkAZgA7ACAARQBGAD0AOwAgAEMATwA9ADAAOwAgAFAARgA9ADAAOwAgAFIATAA9ADAADQAKAA0ACgA;ms-body=dGVzdGluZw== Ms-Conversation-ID: 402464421 Content-Type: application/sdp Content-Length: 220 Authorization: Kerberos qop="auth", opaque="32ED9432", realm="SIP Communications Service", targetname="sip/LUOCSHOME.University.liberty.edu", crand="1a610bae", cnum="8", response="602306092A864886F71201020201011100FFFFFFFF235828FB996DD9C397385CBCA591B6E9" v=0 o=- 0 0 IN IP4 10.66.60.52 s=session c=IN IP4 10.66.60.52 t=0 0 m=message 5061 sip null a=accept-types:text/plain text/html image/gif application/im-iscomposing+xml application/ms-imdn+xml text/x-msmsgsinvite MESSAGE END >>>>>>>>>> SIP - 2014-01-24T18:21:35.080386Z (13:21:35) sipe: Read error: Connection reset by peer (104) (13:21:35) connection: Connection error on 0x271d680 (reason: 0 description: Read error) (13:21:35) sipe: Server has disconnected (13:21:35) account: Disconnecting account klarmstrong2,university.liberty.edu\klarmstrong2 (0x1d8c380) (13:21:35) connection: Disconnecting connection 0x271d680 (13:21:35) stun: using server (13:21:35) sipe: SIP transactions count:2 after addition (13:21:35) sipe: MESSAGE START >>>>>>>>>> SIP - 2014-01-24T18:21:35.105088Z BYE sip:jmhoch SIP/2.0 Via: SIP/2.0/tls 10.66.60.52:44738 From: <sip:klarmstrong2>;tag=746662575;epid=41d171354cee To: <sip:jmhoch> Max-Forwards: 70 CSeq: 2 BYE User-Agent: Purple/2.10.7 Sipe/1.18.0 (linux-x86_64; RTC/3.5) Call-ID: 9826gF660aE774iB5F4m4DD3tC057bC674x0E3Ex Content-Length: 0 Authorization: Kerberos qop="auth", opaque="32ED9432", realm="SIP Communications Service", targetname="sip/LUOCSHOME.University.liberty.edu", crand="8394b9d0", cnum="9", response="602306092A864886F71201020201011100FFFFFFFF4300D7422A78619976D91A2EC0AFB352" MESSAGE END >>>>>>>>>> SIP - 2014-01-24T18:21:35.105088Z As you can see, I'm using Kerberos for auth, as I can no longer get NTLM to work for this (even though it was the other way around in Fedora 19). Here's a portion of the packet capture at the exact moment that Pidgin logs me out: 395 2014-01-24 13:21:16.996387000 10.254.4.39 10.66.60.52 TLSv1 1007 Application Data 396 2014-01-24 13:21:17.035909000 10.66.60.52 10.254.4.39 TCP 66 44738 > sip-tls [ACK] Seq=15034 Ack=184797 Win=74752 Len=0 TSval=80300969 TSecr=34948008 397 2014-01-24 13:21:17.102432000 10.254.4.39 10.66.60.52 TCP 66 [TCP Dup ACK 393#1] https > 47271 [ACK] Seq=8061 Ack=3281 Win=63028 Len=0 TSval=34948009 TSecr=80300912 577 2014-01-24 13:21:35.102029000 10.66.60.52 10.254.4.39 TLSv1 332 Application Data, Application Data 578 2014-01-24 13:21:35.102665000 10.254.4.39 10.66.60.52 TCP 60 sip-tls > 44738 [RST, ACK] Seq=184797 Ack=15300 Win=0 Len=0 I'm getting a connection reset back from the OCS server at the time that the message is sent, so I'm thinking it has something to do with the openssl installation.
ok, So I uninstalled the Fedora provided Pidgin and pidgin-sipe packages. Downloaded the latest Pidgin source 2.10.9, and the older pidgin-sipe source (1.17.3) and recompiled them myself. Was able to get Pidgin to work without logging me out.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.