You are not logged in.
I'm using pidgin for MSN instant messaging, and I use NetworkManager for handling wifi and network on my laptop.
When pidgin starts, networkmanager has not yet connected to the wireless network with internet access, so pidgin fails to connect to the MSN account.
After a few seconds I got internet access, but pidgin is still not able to connect when pressing 'reconnect'.
In order to connect to the MSN network I have to restart pidgin.
In other words, I have to be connected to the internet before launching pidgin to login to to my MSN account.
I guess that this problem occurs because pidgin only detects which network interface has internet access on startup?
Ayone have the same issue and know a workaround?
Offline
Not exactly the same, but I suspect it has to do with the same problem.
When I switch from my home network to my network at school (or vice-versa) pidgin is not able to reconnect. I had the exact same problem with emesene and I haven't found out how to solve it.
I'm using wicd.
Offline
I have a similar problem with msn and gtalk. Network manager "lags" in the statup because I have to enter the keyring password and then Pidgin acts as as if there still was no network. If I restart Pidgin everything works as expected...
Last edited by VuDu (2008-10-06 19:08:29)
Offline
It seems that Pidgin has no chance to notice a change in the network connection according to this:
http://repos.archlinux.org/viewvc.cgi/p … iew=markup
There you can see the option --disable-nm in ./configure. I think that means disable network manager. You can also check this under the About dialog of Pidgin. There you have
Debugging Information
Arguments to ./configure: '--prefix=/usr' '--sysconfdir=/etc' '--disable-schemas-install' '--disable-meanwhile' '--disable-nm' '--disable-perl' '--disable-gnutls' '--disable-doxygen' '--with-system-ssl-certs=/etc/ssl/certs' 'CFLAGS=-march=i686 -mtune=generic -O2 -pipe' 'CXXFLAGS=-march=i686 -mtune=generic -O2 -pipe'
Print debugging messages: No
Plugins: Enabled
SSL: SSL support is present.
Library Support
Cyrus SASL: Disabled
D-Bus: Enabled
Evolution Addressbook: Disabled
Gadu-Gadu library (libgadu): Internal
GtkSpell: Enabled
GnuTLS: Disabled
GStreamer: Enabled
Mono: Disabled
NetworkManager: Disabled
Network Security Services (NSS): Enabled
Perl: Disabled
Startup Notification: Enabled
Tcl: Enabled
Tk: Enabled
X Session Management: Enabled
XScreenSaver: Enabled
Zephyr library (libzephyr): Internal
Zephyr uses Kerberos: No
Maybe somebody should try to build it with network manager support? But shouldnt this work with the dbus support and networkmanager is not telling pidgin that something has changed with the connection?
Offline
There's new version. 2.5.2. Try
Offline
There's new version. 2.5.2. Try
I did it, see here: http://bbs.archlinux.org/viewtopic.php?id=57428
Offline
Try this patched version of pidgin which has networkmanager support enabled. The arch package usually does not have this.
http://student.physik.uni-mainz.de/~aneiser/pidgin/ I reported this upstream here: http://developer.pidgin.im/ticket/7323
Last edited by aneiser (2008-10-22 18:03:42)
Offline
I just yaourt -Sb pidgin to use nm, removed de disable flag on the PKGBUILD and it's the same... it won't detect the connection.
In the about dialog I can see that it has network manager support, so it doesn't seem to be the problem.
Offline
I just yaourt -Sb pidgin to use nm, removed de disable flag on the PKGBUILD and it's the same... it won't detect the connection.
In the about dialog I can see that it has network manager support, so it doesn't seem to be the problem.
Yeah this is why I *patched* pidgin's source code so that it works... See here http://developer.pidgin.im/ticket/7323 or take a closer look at my custom PKGBUILD which includes the patch here http://student.physik.uni-mainz.de/~ane … n/PKGBUILD...Did you try my precompiled package here http://student.physik.uni-mainz.de/~ane … pkg.tar.gz
Offline
Nope, I'll try it now
EDIT: seems to be working good now I'll keep testing it, and report back on the next days if the problems happens again
Last edited by VuDu (2008-10-22 19:15:56)
Offline
EDIT: seems to be working good now I'll keep testing it, and report back on the next days if the problems happens again
I uploaded another slightly differently patched version to http://student.physik.uni-mainz.de/~aneiser/pidgin/ Would be nice if everybody who's interested in it would test this version...
Offline
I've been testing it and it doesn't seems to work for every situation.
On the startup it seems to auto-connect when NM connects, but it doesn't seems to work that well when NM losts connection and gets it back.
What's changed on v2? They seem to be completely different, do we have to apply both, or just the latter?
Last edited by VuDu (2008-10-23 17:11:21)
Offline
I've been testing it and it doesn't seems to work for every situation.
On the startup it seems to auto-connect when NM connects, but it doesn't seems to work that well when NM losts connection and gets it back.
What's changed on v2? They seem to be completely different, do we have to apply both, or just the latter?
Just to understand it correctly: v2 does not work when pidgin is started when the network is disconnected, then pidgin does not react on a network change? Please describe a bit more in detail what happens with the "new" version. And did you check that with v1 and there it worked? So it is a regression?
Well, v2 and v1 use different approaches and I don't if maybe both are just a "bad" workaround for a bug which lies somewhere else.
Offline
I was talking about the v1 patch. I'm going to test the v2 now
Offline
I was talking about the v1 patch. I'm going to test the v2 now
Well, in the meantime someone with more knowledge about pidgin has developed a better fix for this problem (see bugtracker link in previous post). I uploaded the new patched version of pidgin to http://student.physik.uni-mainz.de/~aneiser/pidgin/
Offline