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 358258 - crash in Gossip Instant Messenger: Connecting to a jabber s...
crash in Gossip Instant Messenger: Connecting to a jabber s...
Status: RESOLVED DUPLICATE of bug 346994
Product: gossip
Classification: Deprecated
Component: General
0.17
Other All
: High critical
: ---
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-29 09:41 UTC by Chris Lord
Modified: 2006-09-29 10:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Chris Lord 2006-09-29 09:41:02 UTC 
What were you doing when the application crashed?
Connecting to a jabber server


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 38699008 vsize: 0 resident: 38699008 share: 0 rss: 16379904 rss_rlim: 0
CPU usage: start_time: 1159522481 rtime: 0 utime: 121 stime: 0 cutime:116 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gossip'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226828112 (LWP 4734)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 73545

Thread 1 (Thread -1226828112 (LWP 4734))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 pthread_mutex_lock
    from /lib/tls/i686/cmov/libpthread.so.0
  • #5 g_source_unref
    from /usr/lib/libglib-2.0.so.0
  • #6 lm_connection_unregister_message_handler
    from /usr/lib/libloudmouth-1.so.0
  • #7 _lm_connection_failed_with_error
    from /usr/lib/libloudmouth-1.so.0
  • #8 _lm_connection_succeeded
    from /usr/lib/libloudmouth-1.so.0
  • #9 g_io_channel_unix_get_fd
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 ??
  • #0 __kernel_vsyscall 






Comment 1


Richard Hult





          2006-09-29 10:33:45 UTC
        



Will mark as dup of the "lm problem bug", looks exactly like one of the two version of stack traces we get.

*** This bug has been marked as a duplicate of 346994 ***