FS#24150 - [pidgin or libpurple] Waiting for network connection

Attached to Project: Arch Linux
Opened by Green (The_Green_Arrow) - Saturday, 07 May 2011, 19:37 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 08 May 2011, 20:19 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Since latest updates of pidgin and libpurple :
upgraded libpurple (2.7.11-1 -> 2.7.11-2)
upgraded pidgin (2.7.11-1 -> 2.7.11-2)
I've got this strange behaviour in pidgin : http://pix.toile-libre.org/upload/original/1304796807.gif

Downgrading to 2.7.11-1 fixes this issue (so this is definitely a packaging issue).


Steps to reproduce:
* upgrade pidgin and libpurple
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Sunday, 08 May 2011, 20:19 GMT
Reason for closing:  Not a bug
Comment by Ionut Biru (wonder) - Saturday, 07 May 2011, 19:51 GMT
let me guess, you don't have networkmanager 0.8.999 ?
Comment by Ionut Biru (wonder) - Saturday, 07 May 2011, 19:58 GMT
let me rephrase that.

you are using networkmanager to manage your networks but not version 0.8.999?
Comment by Green (The_Green_Arrow) - Sunday, 08 May 2011, 06:15 GMT
Precisely
Comment by Ionut Biru (wonder) - Sunday, 08 May 2011, 07:06 GMT
that's not a bug. networkmanager had a soname bump. you need to fix yourself that if you downgrade.

Comment by Green (The_Green_Arrow) - Sunday, 08 May 2011, 18:15 GMT
  • Field changed: Percent Complete (100% → 0%)
Could you please add the following comments to the bug report :

- what I don't understand is why this issue occurs between minor upgrade (there shouldn't be that much difference between pkgrel -1 and pkgrel -2). I mean, pidgin should adapt to the network configuration without any issue like that.


- That being said, adding -f argument to pidgin solves this issue. -f : Try to be online even if the network is reported (by Windows, or NetworkManager on Linux) to be unavailable.

- I do not want to upgrade to Gnome 3 (not until Gnome 3.2 in september). And even if I would, I couldn't because I have an ATI card with fglrx driver. On a laptop, open source drivers are still far from being as good as fglrx (power management, vaapi, etc.)

That's why I've frozen almost every gnome 2 related packages (with my own dedicated local repository).

I've tried to upgrade network manager to the newer version, but there are some errors then (some undefined symbols).
Comment by Ionut Biru (wonder) - Sunday, 08 May 2011, 18:21 GMT
bumping pkgrel can occur for multiple reasons.
pidgin 2.7.11-1 was compiled against networkmanager 0.8.3
pidgin 2.7.11-2 was recompiled against new networkmanager 0.9 rc because libnm-glib.so had a soname bump from
libnm-glib.so.1 to libnm-glib.so.4 therefor a rebuilt was needed


if you don't want to upgrade to gnome 3 then you should stop upgrading or deal with bugs like this because YOU choose to ignore and cherry picks updates.

i don't understand why you asked for a reopen. mostly to talk? i don't have anything to do on this issue. everything works.

what can you do is to switch to wicd or netcfg
Comment by Green (The_Green_Arrow) - Sunday, 08 May 2011, 19:03 GMT
Thanks for the explanation.
I just wanted to reopen to add some comments (mainly about the -f workaround) for other users.
I've tried wicd and it does not work well with my r8192se realtek wireless card . Don't know about netcfg, I'll give it a try.
I know I should not upgrade anything that is related to Gnome, but I did not know pidgin was so much dependent on gnome.

Loading...