After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 319087 - Gossip crashed when opening Edit->Personal details
Gossip crashed when opening Edit->Personal details
Status: RESOLVED FIXED
Product: gossip
Classification: Deprecated
Component: General
0.9
Other Linux
: Normal normal
: ---
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-17 16:33 UTC by Sebastien Bacher
Modified: 2005-12-30 13:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2005-10-17 16:33:15 UTC 
This bug has been opened here: https://bugzilla.ubuntu.com/show_bug.cgi?id=17856

"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:

+ Trace 63574

  • #0 g_type_check_instance_is_a
    from /usr/lib/libgobject-2.0.so.0
  • #1 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #2 jabber_helper_async_get_vcard_cb
    at gossip-jabber-helper.c line 143
  • #3 _lm_message_handler_handle_message
    at lm-message-handler.c line 47
  • #4 connection_incoming_dispatch
    at lm-connection.c line 246
  • #5 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #8 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 main
    at gossip-main.c line 172 






Comment 1


Martyn Russell





          2005-12-30 13:02:09 UTC
        



I haven't seen this in a while, a lot of the code has been reworked recently so I think this has been fixed in the process.  

I am marking this as fixed, let me know if you see this again, and we will reopen it.