This seems a common problem. In my case, Network Manager does not
recognize my modem connection, I've installed a third-party driver. When
I start Pidgin, it keeps 'waiting for connection' when actually I'm
really connected to internet.
I talked with Pidgin's team: they say we have a build with NM
integration, and this integration does not work fine, saying that NM
sucks. This is what happens: Pidgin keeps waiting for NM to provide a
connection, however it doesn't, because can't see my dialled one. Then
you have to e.g. change status to off and again to on, so that Pidgin
now *ignores* NM and try to connect anyway.
I proposed a very simple solution but they simply rejected: when Pidgin
starts it could try to connect anyway: on fail, then it **keeps silent**
and **waiting for NM**. They just didn't accepted the suggestion, they
say it's a workaround and that they can't ignore NM, but do not apply
this approach as a whole (making Pidgin completely inaccessible), e.g.
when changing status. I don't think as a workaround but the 1st most
natural thing to do: just try to connect. It's the better way to know if
we have a connection, not trust on another secondary software which we
can't always trust.
I think this bug is STUPID and it makes me think even more how Pidgin
sucks. It's stupid and ridiculous having to change status EVERY DAY to
connect. And I think Pidgin's team sucks too. Hope now that Ubuntu apply
my SIMPLE suggestion to solve this [EMAIL PROTECTED] bug! (sorry)
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
pidgin won't connect until I change the "status"
https://bugs.launchpad.net/bugs/180326
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
