[Bug 17856] New: Gossip crashed when opening Edit->Personal details

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=17856
Ubuntu | gossip

           Summary: Gossip crashed when opening Edit->Personal details
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gossip
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: andre.bugs at gmail.com
         QAContact: desktop-bugs at lists.ubuntu.com


This evening I noticed that Gossip crashed as soon as I went to Edit->Personal
details. This has not happened in the past (with the same version of Gossip), so
I'm guessing it could be some weirdness with the Jabber server that is
triggering some bug in Gossip. I'm using Gossip version 0.9-1 and
libloudmouth1-0 version 1.0.1-1 on Ubuntu 5.10.

Below is a backtrace of the crash:

#0  0xb79a69a1 in g_type_check_instance_is_a () from /usr/lib/libgobject-2.0.so.0
#1  0xb798f876 in g_object_unref () from /usr/lib/libgobject-2.0.so.0
#2  0x08085526 in jabber_helper_async_get_vcard_cb (handler=0x82260f8,
connection=0x81b5200, m=0x82476d8, data=0x823fcd0) at gossip-jabber-helper.c:143
#3  0xb7a56e54 in _lm_message_handler_handle_message (handler=0x82260f8,
connection=0x81b5200, message=0x82476d8) at lm-message-handler.c:47
#4  0xb7a54cdf in connection_incoming_dispatch (source=0x754c000, callback=0,
user_data=0x0) at lm-connection.c:246
#5  0xb79154ee in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#6  0xb79184f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#7  0xb79187e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#8  0xb7d2ae65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#9  0x0806d7be in main (argc=1, argv=0xbf8e4a04) at gossip-main.c:172

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.