Description of problem: I did "yum update" last night which comes with "pidgin-sipe-1.15.0-1" and "purple-sipe-1.15.0-1". I can't connect to Communicator any more after that. I got "authentication error" message from Pidgin. I downgraded to the older version 1.14 and it started working again. Version-Release number of selected component (if applicable): Mar 18 23:28:09 Updated: purple-sipe-1.15.0-1.fc18.x86_64 Mar 18 23:28:12 Updated: pidgin-sipe-1.15.0-1.fc18.x86_64 How reproducible: Start pidgin and it won't connect to Communicator. Steps to Reproduce: 1. Start Pidgin 2. 3. Actual results: It won't connect, displays authentication error. Expected results: connects to communicator. Additional info:
Log file is missing. Please read the update message: * unified Single Sign-On (SSO) handling in all places * if SSO has been selected then Login & Password will be **ignored**! * please make sure to check the settings of existing accounts after updating Please check the "Use Single Sign-On" setting on the Advanced tab. If you are using NTLM it must be off, because NTLM does not support Single Sign-On.
Is there documentation that is easily findable for this change in the SSO setting? The update from yum -y update is shown below, so even if I had been paying attention there wouldn't have been anything to notice...where is the update message supposed to appear? Now that I *know* what the problem is, google finds the pidgin FAQ with exactly this answer. But I had to know that SSO was the issue :-( For kicks and grins, I went to my preferences, changed the settings to generate system logs for pidgin, reenabled SSO, quit pidgin and relaunched. It fails to connect but there is no log. ---- 260 root> yum -y update Loaded plugins: langpacks, presto, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package pidgin-sipe.x86_64 0:1.13.1-1.fc17 will be updated ---> Package pidgin-sipe.x86_64 0:1.15.0-1.fc17 will be an update ---> Package purple-sipe.x86_64 0:1.13.1-1.fc17 will be updated ---> Package purple-sipe.x86_64 0:1.15.0-1.fc17 will be an update --> Finished Dependency Resolution Dependencies Resolved ==================================================================================================================================== Package Arch Version Repository Size ==================================================================================================================================== Updating: pidgin-sipe x86_64 1.15.0-1.fc17 updates 27 k purple-sipe x86_64 1.15.0-1.fc17 updates 264 k Transaction Summary ==================================================================================================================================== Upgrade 2 Packages Total download size: 291 k Downloading Packages: Setting up and reading Presto delta metadata (1/2): pidgin-sipe-1.15.0-1.fc17.x86_64.rpm | 27 kB 00:00 (2/2): purple-sipe-1.15.0-1.fc17.x86_64.rpm | 264 kB 00:00 ------------------------------------------------------------------------------------------------------------------------------------ Total 273 kB/s | 291 kB 00:01 Running Transaction Check Running Transaction Test Transaction Test Succeeded Running Transaction Updating : purple-sipe-1.15.0-1.fc17.x86_64 1/4 Updating : pidgin-sipe-1.15.0-1.fc17.x86_64 2/4 Cleanup : pidgin-sipe-1.13.1-1.fc17.x86_64 3/4 Cleanup : purple-sipe-1.13.1-1.fc17.x86_64 4/4 Verifying : pidgin-sipe-1.15.0-1.fc17.x86_64 1/4 Verifying : purple-sipe-1.15.0-1.fc17.x86_64 2/4 Verifying : purple-sipe-1.13.1-1.fc17.x86_64 3/4 Verifying : pidgin-sipe-1.13.1-1.fc17.x86_64 4/4 Updated: pidgin-sipe.x86_64 0:1.15.0-1.fc17 purple-sipe.x86_64 0:1.15.0-1.fc17 Complete!
(In reply to comment #2) > Is there documentation that is easily findable for this change in the SSO > setting? The update from yum -y update is shown below, so even if I had been > paying attention there wouldn't have been anything to notice...where is the > update message supposed to appear? > > Now that I *know* what the problem is, google finds the pidgin FAQ with > exactly this answer. But I had to know that SSO was the issue :-( It is in the FAQ, in the new "how to set up an account" wiki page, on the README displayed on the SIPE 1.15.0 download page, on the news entry for SIP 1.15.0 and in every 1.15.0 update document (Changelog, NEWS, bodhi note, package history). The problem is that previously SIPE set SSO to "ON" for new accounts. But the SSO flag was only checked at random places, i.e. if SSO DID NOT work for you simply didn't notice :-/ Now the SSO flag is checked the same way at every place and therefore its setting must be correct. Unfortunately this is one of the places were cleaning up the §$%$$§ code has end-user visible side effects :-/
(In reply to comment #2) > For kicks and grins, I went to my preferences, changed the settings to > generate system logs for pidgin, reenabled SSO, quit pidgin and relaunched. > It fails to connect but there is no log. The "Debug Window" is one of those great UI design decisions of the Pidgin developers. IMHO that menu entry should only be visible when the user has started pidgin with the --debug command line option. "System logs" is not the same as the debug log. Almost every user makes this mistakes and sends incomplete logs :-(
Thanks. I do confirm the problem is fixed by "unchecking" SSO.
Thanks for confirming. *** This bug has been marked as a duplicate of bug 922895 ***