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 351068 - crash on Gossip Instant Messenger
crash on Gossip Instant Messenger
Status: RESOLVED DUPLICATE of bug 349649
Product: gossip
Classification: Deprecated
Component: General
0.12
Other All
: High critical
: ---
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-12 18:12 UTC by adebarbara
Modified: 2006-08-14 12:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description adebarbara 2006-08-12 18:12:59 UTC
What were you doing when the application crashed?
Running gossip in a remote X generate this error.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.91 2006-08-08 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 20922368 vsize: 0 resident: 20922368 share: 0 rss: 8187904 rss_rlim: 0
CPU usage: start_time: 1155406274 rtime: 0 utime: 17 stime: 0 cutime:15 cstime: 0 timeout: 2 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 -1226926416 (LWP 19584)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226926416 (LWP 19584))

  • #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 __kernel_vsyscall
  • #5 *__GI_raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 *__GI_abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 galago_init
    from /usr/lib/libgalago.so.2
  • #10 gossip_galago_init
  • #11 main
  • #0 __kernel_vsyscall

Comment 1 Martyn Russell 2006-08-14 07:27:20 UTC
Can you reproduce this in 0.14?

We fixed a couple of crashers and a lot of memory/reference issues with GObjects between 0.12 and 0.14.
Comment 2 Richard Hult 2006-08-14 12:24:08 UTC
This bug is because of galago (wrongly) aborts when it can't find dbus. We are working around that since 0.14. Closing as a dup of the original bug.

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