Gaim crashes while getting roomlist

Hello Soroosh,

Thank you for the bug report, I was wondering if I could get you to note down the version & flavour of Ubuntu that you are using please, also the version of Gaim as well? This is aid us greatly in tracking down your problem.

Thanks again, Alex.

I am using ubuntu edgy and the latest gaim from ubuntu repository + upstream cvs build of gaim and here is the backtrace:
#0 0xb75dc722 in g_type_check_instance_cast ()
   from /usr/lib/libgobject-2.0.so.0
#1 0x080c26c4 in gaim_gtk_roomlist_init ()
#2 0xb7532dd6 in g_source_get_current_time () from /usr/lib/libglib-2.0.so.0
#3 0xb7532802 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#4 0xb75357df in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#5 0xb7535b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#6 0xb7b55574 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#7 0x080abf49 in main ()

Hello Soroosh,

Thank you for your comments, I believe we now have a complete report, I have sent the bug upstream to the Gaim Bug Tracker, I have also confirmed the bug report so the developers can now have a look it.

Thanks again, Alex

do you use gaim from ubuntu or upstream? We don't support non-packaged versions. If you use the Ubuntu version could you get a backtrace with gaim-dbg installed?

#0 0xb68ddb29 in yahoo_roomlist_got_connected (data=0x8620860, source=19, cond=GAIM_INPUT_READ)
    at ../../../../src/protocols/yahoo/yahoochat.c:1344
#1 0x080995d4 in no_one_calls (data=0x8627588, source=19, cond=GAIM_INPUT_WRITE)
    at ../../src/proxy.c:980
#2 0x080fafe3 in gaim_gtk_io_invoke (source=0x860c878, condition=G_IO_OUT, data=0x8625370)
    at ../../src/gtkeventloop.c:74
#3 0xb7916c8d in g_io_channel_unix_get_fd () from /usr/lib/libglib-2.0.so.0
#4 0xb78ed802 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#5 0xb78f07df in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#6 0xb78f0b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#7 0xb7c22574 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#8 0x0810fd0c in main (argc=C

and I tested these vesions:
ubuntu package (beta3)
beta5

Thank you for the details about that

No crash file attached to this bug. Please reopen if you get a crash with pidgin. The link to the upstream bug gives an error message.

Here is a backtrace from Intrepid:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f86ff79d770 (LWP 22353)]
0x00007f86eb951273 in yahoo_roomlist_got_connected (data=0x304b960, source=26,
    error_message=0x0)
    at ../../../../libpurple/protocols/yahoo/yahoochat.c:1448
1448 ../../../../libpurple/protocols/yahoo/yahoochat.c: No such file or directory.
 in ../../../../libpurple/protocols/yahoo/yahoochat.c
(gdb) bt
#0 0x00007f86eb951273 in yahoo_roomlist_got_connected (data=0x304b960,
    source=26, error_message=0x0)
    at ../../../../libpurple/protocols/yahoo/yahoochat.c:1448
#1 0x00007f86fc62b837 in purple_proxy_connect_data_connected (
    connect_data=0x304b070) at ../../libpurple/proxy.c:598
#2 0x00007f86fc62d5e5 in s5_canread_again (data=0x304b070, source=26,
    cond=PURPLE_INPUT_READ) at ../../libpurple/proxy.c:1389
#3 0x000000000046ded1 in pidgin_io_invoke (source=0x3049a80,
    condition=G_IO_IN, data=0x304a1a0) at ../../pidgin/gtkeventloop.c:78
#4 0x00007f86fc904d3b in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#5 0x00007f86fc90850d in ?? () from /usr/lib/libglib-2.0.so.0
#6 0x00007f86fc908a3d in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#7 0x00007f86fdaae7a7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#8 0x000000000048a9f5 in main (argc=1, argv=0x7fff077d10b8)
    at ../../pidgin/gtkmain.c:887

Soroosh,

Does this crash seem to be random, or can you repeat it? If its repeatable, can you provide the steps to repeat this?

Thank you.

Hi. Upstream bug http://developer.pidgin.im/ticket/6134 looks very similar to this bug, but that one is supposed to be fixed in 2.4.2 already. Also I'm unable to reproduce this.

@ Soroosh: Do you still have this issue in Intrepid up-to-date? If so, please attach a fresh backtrace (https://wiki.ubuntu.com/Backtrace) and a debug log (pidgin --debug) to this report.

Thanks in advance
//magnus

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!