gaim chashed when connection to wildfire (jabber) server (gaim_gtk_blist_request_add_buddy)

Bug #78913 reported by James
4
Affects Status Importance Assigned to Milestone
gaim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gaim

Hi,

This crash report was created after attempting to connect to a wildfire server.

I'm unable to reproduce this bug. After restarting gaime, it connected without any problems.

Hope that this helps someone.

Revision history for this message
James (jneethling) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug

Changed in gaim:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Debug backtrace (gaim2.0beta3.1):

"...
#0 0x080d3ce5 in gaim_gtk_blist_request_add_buddy (account=<value optimized out>, username=0x0,
    group=0x83958e0 "Individuals", alias=0x0) at ../../src/gtkblist.c:4514
        table = <value optimized out>
        label = <value optimized out>
        hbox = <value optimized out>
        vbox = <value optimized out>
        img = <value optimized out>
#1 0x080d4b0e in gaim_gtk_blist_add_buddy_cb () at ../../src/gtkblist.c:822
        sel = <value optimized out>
        iter = {stamp = 1382148705, user_data = 0x8473168, user_data2 = 0x0, user_data3 = 0x0}
        node = (GaimBlistNode *) 0x83958f0
#2 0xb79ccb29 in IA__g_cclosure_marshal_VOID__VOID (closure=0x85301b8, return_value=0x0, n_param_values=1,
    param_values=0xbfaf9bac, invocation_hint=0xbfaf9abc, marshal_data=0x80d4a50) at gmarshal.c:77
        data1 = (gpointer) 0x855e6e8
        data2 = (gpointer) 0x0
        __PRETTY_FUNCTION__ = "IA__g_cclosure_marshal_VOID__VOID"
#3 0xb79bf79b in IA__g_closure_invoke (closure=0x85301b8, return_value=0x0, n_param_values=1, param_values=0xbfaf9bac,
    invocation_hint=0xbfaf9abc) at gclosure.c:490
        marshal = (GClosureMarshal) 0x806d7d4 <g_cclosure_marshal_VOID__VOID@plt>
        marshal_data = (gpointer) 0x0
        __PRETTY_FUNCTION__ = "IA__g_closure_invoke"
#4 0xb79cfb93 in signal_emit_unlocked_R (node=0x83844d0, detail=0, instance=0x855e6e8, emission_return=0x0,
    instance_and_params=0xbfaf9bac) at gsignal.c:2440
        tmp = <value optimized out>
        handler = (Handler *) 0x853b440
        accumulator = (SignalAccumulator *) 0x0
        emission = {next = 0xbfaf9fc4, instance = 0x855e6e8, ihint = {signal_id = 107, detail = 0,
    run_type = G_SIGNAL_RUN_FIRST}, state = EMISSION_RUN, chain_type = 4}
        class_closure = (GClosure *) 0x83844b8
        handler_list = (Handler *) 0x853b440
        return_accu = (GValue *) 0x0
        accu = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0,
      v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0,
      v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
        signal_id = 107
        max_sequential_handler_number = 1123
        return_value_altered = 1
..."

Revision history for this message
Adam Niedling (krychek) wrote :

Edgy and gaim are not supported anymore. Please open a new bug if you get a crash with pidgin in a later version of Ubuntu.

Changed in gaim:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.