Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1165066 - Pidgin 2.10.10 can't connect to MSN
Summary: Pidgin 2.10.10 can't connect to MSN
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Synacek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1172124
TreeView+ depends on / blocked
 
Reported: 2014-11-18 09:19 UTC by Xavier Bachelot
Modified: 2014-12-09 12:47 UTC (History)
5 users (show)

Fixed In Version: pidgin-2.10.11-1.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1172124 (view as bug list)
Environment:
Last Closed: 2014-12-03 01:01:17 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Xavier Bachelot 2014-11-18 09:19:45 UTC 
Description of problem:
Pidgin can't connect to MSN and status stays at "Available - connecting".

Version-Release number of selected component (if applicable):
2.10.10-1.fc20

How reproducible:
Always

Steps to Reproduce:
1. Configure MSN account
2. Enable MSN account
3.

Actual results:
No connection to MSN network

Expected results:
Connection to MSN network

Additional info:
Upstream bug : https://developer.pidgin.im/ticket/16455
Upstream fix : https://hg.pidgin.im/pidgin/main/rev/f6a91e6c77a4
Comment 1 Fedora Update System 2014-11-18 11:45:22 UTC 
pidgin-2.10.10-3.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/pidgin-2.10.10-3.fc21
Comment 2 Fedora Update System 2014-11-18 12:22:58 UTC 
pidgin-2.10.10-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/pidgin-2.10.10-2.fc20
Comment 3 Jan Synacek 2014-11-18 12:35:41 UTC 
http://pkgs.fedoraproject.org/cgit/pidgin.git/commit/?h=f20&id=1334fb92d458fbcabffb81b7a8be716e2199723a
Comment 4 Fedora Update System 2014-11-19 03:07:56 UTC 
Package pidgin-2.10.10-3.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pidgin-2.10.10-3.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-15330/pidgin-2.10.10-3.fc21
then log in and leave karma (feedback).
Comment 5 Xavier Bachelot 2014-11-20 11:18:23 UTC 
The ID just added by the patch was working for the last few days, but is not working anymore. It got replaced again upstream : https://hg.pidgin.im/pidgin/main/raw-rev/e1fa63d0bdaa
I locally rebuilt a patched pidgin version and I'm able to connect again.
Comment 6 Jan Synacek 2014-11-20 14:30:49 UTC 
Well, that is annoying...

http://pkgs.fedoraproject.org/cgit/pidgin.git/commit/?h=f20&id=aed50b5245524cae0a6e7b76ef63b2991f46fbce
Comment 7 Fedora Update System 2014-11-20 14:33:53 UTC 
pidgin-2.10.10-4.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/pidgin-2.10.10-4.fc21
Comment 8 Fedora Update System 2014-11-20 14:40:38 UTC 
pidgin-2.10.10-3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/pidgin-2.10.10-3.fc20
Comment 9 Fedora Update System 2014-11-25 14:40:07 UTC 
pidgin-2.10.11-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/pidgin-2.10.11-1.fc21
Comment 10 Fedora Update System 2014-12-03 01:01:17 UTC 
pidgin-2.10.10-3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 11 Fedora Update System 2014-12-06 10:45:25 UTC 
pidgin-2.10.11-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.