pidgin won't connect until I change the "status"

[glopv2]

Binary package hint: pidgin

When I run pidgin, it says "waiting" and is not actually connecting. If I then change the status (for instance, from "available" to "away") then pidgin changes to "connecting" and shortly thereafter connects successfully.

ProblemType: Bug
Architecture: i386
Date: Fri Jan 4 03:47:56 2008
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.1.1-0landure1
PackageArchitecture: i386
ProcCmdline: pidgin
ProcCwd: /home/robert
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux johnnycash 2.6.20-16-generic #2 SMP Tue Dec 18 05:45:12 UTC 2007 i686 GNU/Linux
UnreportableReason: This is not a genuine Ubuntu package

[Display Name (user340562791542-deactivatedaccount)]

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 FU...@#$% bug! (sorry)

[Eduardo Retamales (eretamales)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in Pidgin.

[Brian Murray (brian-murray)]

I'm unassigning the bug report as assignment should be used when a bug is In Progress and someone is working on a fix.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Renato which version of Network Manager have you noticed this with? Network manager has undergone quite a few changes since this was originally reported about Feisty. Thanks in advance.

[Display Name (user340562791542-deactivatedaccount)]

Hi Brian, I'm on Windows right now, but the version is simply the latest available in all the times, since I always update my Ubuntu. I'm using Gutsy now.

[Basilio Kublik (sourcercito)]

Hi Renato
is this still an issue under an up to date Hardy Heron system?

Thanks in advance.

[Display Name (user340562791542-deactivatedaccount)]

Hi Basilio, I didn't install Hardy yet but will tell you when I do.

[Alexander Sack (asac)]

this is a dupe for a similar firefox bug. but certainly a problem with network manager -> the online/offline state.

[Display Name (user340562791542-deactivatedaccount)]

Huh?

[Jess Bermudes (jbermudes)]

I have also encountered this bug in 8.04 and pidgin. When connecting on 56k, I must also change states in order for pidgin to connect.

[Display Name (user340562791542-deactivatedaccount)]

As I've said above, the solution is quite simple, but it seems no one wants to code it.

It's a crap. Pidgin relies on NM when you're starting as online, but it DOESN'T when you change your status (workaround). It should still wait a connection from NM or either (the solution) just try to connect when started.

[Leonard Michlmayr (leonard-michlmayr)]

I think instead of adding a workaround to each program that uses nm, nm should be fixed. It cannot be that hard. (If the nm-code would be documented I would do it by myself.)

NM does not use dial-up connections, ok. But you have another way to dial up, right? So why not have a script that tells nm about the ppp-connection in /etc/network/if-up.d and /etc/network/if-down.d ?

All I need is command-line interface to nm that lets me tell nm “Hey I have a network inteface of type $(gettext dial-up) with the name ppp0 that is {connected|offline} now.”

(An a cool thing would be “I have a network interface of type $(gettext dial-up) which could connect to the internet if you call ifup ppp0.” But that might be too advanced.)

[Display Name (user340562791542-deactivatedaccount)]

Nice idea Leonard!

[Alexander Menk (alex-menk)]

Hi!

this problem still exists in Karmic. The impact is very silly, I still can not use pidgin to chat (and somehow I think Empathy does not work better with that)

I like Leonard's suggestion. We really should try to make a patch for that. Anybody volunteer or tried already something like that? I am not very good in C++ though :(

Alex

[Evžen Šubrt (evzen-subrt)]

Hi!

I searched the net and I have by accident came across the advice to run pidgin with -f option, i.e.
pidgin -f
I am using T-Mobile 4G USB modem which is not detected by the NM and with the -f option, Pidgin connects OK.
I am using Ubutnu 9.10 Keramic Koala.

Btw. Empathy client is also affected by the "no connection in NM" bug, but so far i have not found solution/workaround for it.