Hello Ludovico,

>>on Debian sid it crashes when logging out e logging back in.
Yes, there is a bug with libpurple.
It appends on win 32 too.

I have commited a fix for that : 


diff -r f7cc052777c2 -r 8f033f2ab21a 
libs/3rdparty/libpurple/pidgin-2.5.1/libpurple/prefs.c
--- a/libs/3rdparty/libpurple/pidgin-2.5.1/libpurple/prefs.c Fri Oct 10 
11:40:39 2008 +0200
+++ b/libs/3rdparty/libpurple/pidgin-2.5.1/libpurple/prefs.c Fri Oct 10 
11:52:15 2008 +0200
@@ -1388,6 +1388,7 @@

prefs_hash = g_hash_table_new_full(g_str_hash, g_str_equal, g_free, NULL);

+ prefs.first_child = 0;
purple_prefs_connect_callback(handle, "/", prefs_save_cb, NULL);

purple_prefs_add_none("/purple");
@@ -1452,4 +1453,6 @@
}

purple_prefs_disconnect_by_handle(purple_prefs_get_handle());
+ g_hash_table_destroy(prefs_hash);
+ prefs_hash = 0;
}


Laurent

----- Original Message ----- 
From: "Ludovico Cavedon" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, December 11, 2008 10:25 AM
Subject: Re: Crash adding IM account on 64bit


> On Tue, Dec 9, 2008 at 8:24 AM, Andreas Schneider <[EMAIL PROTECTED]> wrote:
>> On Tuesday 09 December 2008 09:33:25 Ludovico Cavedon wrote:
>>> Anyway, here it is the patch in order to use system libpurple, simpler
>>> than expected :)
>>> And it seems to work with the latest libpurple in Debian sid (2.5.2)!
>>
>> Woohooo. That's great! :)
> 
> Now come the bad news: using the external libpurple on Debian sid it
> crashes when logging out e logging back in. I guess some reace
> conditions comes up :(
> 
> Here is an updated version of the patch (with a fix I forgot for the
> "make install" part) that does not enable external libpurple by
> default. I would suggest applying this patch, do people can try and
> build it with LIBPURPLE_INTERNAL=OFF
> 
> Thanks,
> Ludovico
>


--------------------------------------------------------------------------------


> _______________________________________________
> QuteCom-dev mailing list
> [email protected]
> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to