pidgin 2.6.6 "waiting for network connection" not using network-manager

[b]

Since I start pidgin on startup and don't use it that often during the week I only noticed this recently.

Pidgin is no longer connecting to the servers unless I put "-f" after it. It was working fine before with the same configuration, so the problem must have been recent updates.

All the references I can find online for this problem are related to network-manager, which I don't believe is running:

$ ps aux | grep nm
bbogart 2170 0.0 0.0 8700 896 pts/1 S+ 09:19 0:00 grep --color=auto nm

I'll add the -f flag to start up pidgin from now on, but this seems like a degraded update to me.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pidgin 1:2.6.6-1ubuntu4.4
ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
Uname: Linux 2.6.32-38-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Feb 7 09:14:18 2012
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.utf8
 SHELL=/bin/bash
SourcePackage: pidgin
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1354): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (tomboy:1334): libtomboy-WARNING **: Binding '<Alt>F12' failed!
 (tomboy:1334): libtomboy-WARNING **: Binding '<Alt>F11' failed!
 (tomboy:1334): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.

[Bryan Quigley (bryanquigley)]

Thanks for reporting this bug and helping make Ubuntu better. Sorry we don't always have the resources to get to every bug report. Ubuntu 10.04 is no longer supported so I'm going to close the bug.