Description of problem: When pidgin opens up it doesn't connect to my active accounts. To get it working I need to go into the accounts page, deactivate all my accounts. Then Activate again. Then everything works normally.
What version of pidgin do you have installed?
pidgin.x86_64 2.7.10-1.fc15
I believe the NetworkManager 0.9 compatibility patch that went in to 2.7.10-2.fc15 (and is in 2.7.11-1.fc15) should fix this.
I have 2.7.11-1 and actually just started noticing this problem. Incidentally, I've finally upgraded NM to 0.9-pre: NetworkManager-0.8.997-4.git20110325.fc15.x86_64 after uninstalling the 3rd-party NM add-ons that have not been rebuilt for it. So the problem is *not* fixed -- can I provide any information to debug this? Thanks.
The following combination works for me: NetworkManager-0.8.997-4.git20110325.fc15.x86_64 pidgin-2.7.11-2.fc15.x86_64 Oddly enough, pidgin-2.7.11-2.fc16.x86_64 does not work with NetworkManager-0.8.997-4.git20110325.fc16.x86_64 in my Rawhide installation; I had to downgrade to pidgin-2.7.11-2.fc15.x86_64
I'm assigning to NetworkManager because nothing has changed in Pidgin other than the rebuilds/patches applied by the NetworkManager maintainer. Pidgin debug logs from "Help->Debug Window" around the time this problem occurs may help.
*** Bug 691174 has been marked as a duplicate of this bug. ***
Dan, I can see this too. A workaround for me is that, after NetworkManager has established a wireless connection, relogging in, works. It seems the patch you have provided makes pidgin fails to connect after NM establishes a connection but if a connection already exists, pidgin recognizes that.
Don't have this bug with NetworkManager.x86_64-0.8.2-8.git20101117.fc15 and pidgin.x86_64-2.7.11-1.fc15. Those seem to be the latest versions?! So what is this bug about?
After todays update, I have this working with: NetworkManager.x86_64 1:0.8.997-6.git20110328.fc15 pidgin.x86_64 2.7.11-2.fc15 So still, everything okay. No bug far and wide ...
Discussed at the 2011-04-01 blocker bug meeting. Rejected as beta blocker as it doesn't hit any beta criterion.
The mega-update already listed has the necessary fixes. If that update does not fix the problem, lets re-open. https://admin.fedoraproject.org/updates/pidgin-2.7.11-2.fc15,telepathy-glib-0.14.1-1.fc15,telepathy-logger-0.2.6-1.fc15,libsocialweb-0.25.11-3.fc15,kdebase-runtime-4.6.1-3.fc15,epiphany-2.91.92-2.fc15,evolution-2.91.92-2.fc15,control-center-2.91.92-3.fc15,kde-plasma-networkmanagement-0.9-0.44.20110323.fc15,kdebase-workspace-4.6.1-5.fc15,empathy-2.91.92-2.fc15,geoclue-0.12.0-7.fc15,krb5-auth-dialog-2.91.91-3.fc15,gnome-shell-2.91.92-3.fc15,NetworkManager-openvpn-0.8.995-1.fc15,NetworkManager-vpnc-0.8.996-2.fc15,NetworkManager-0.8.997-4.git20110325.fc15,NetworkManager-openswan-0.8.0-9.20100411git.fc15,tracker-0.10.3-3.fc15,NetworkManager-pptp-0.8.995-1.fc15,NetworkManager-openconnect-0.8.1-7.git20110326.fc15,openconnect-3.01-2.fc15,liferea-1.6.5-4.fc15,claws-mail-3.7.8-7.fc15,nntpgrab-0.6.91-4.fc15
Just wanted to re-open this as the problem never was fixed. Something else. My network connect isn't currently controlled by NetworkManager. (I've bridge my network which I believe NM can't handle at the moment) Which might have something to do with this, as empathy is reporting no network connection.
Actually confirmed. If you have your primary network card bridged, which means NetworkManager has no active connections, none of the pidgin or empathy connections startup on login. With pidgin you can get everything working unchecking and rechecking the accounts. empathy no such luck.
*** Bug 693113 has been marked as a duplicate of this bug. ***
Dann, this still doesn't work. In your blog you wrote that all patches are available and I see them in git, however pidgin-2.7.11-2.fc15 still cannot get online.
Launching pidgin with -f option will force it to believe it is online
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping