Bug 350556 – Critical warning when connecting

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 350556 - Critical warning when connecting


Summary:	Critical warning when connecting


Status:	RESOLVED FIXED

Product:	gossip
Classification:	Deprecated
Component:	General
Version:	0.14
Hardware:	Other All

Importance:	High normal
Target Milestone:	---
Assigned To:	Gossip Maintainers
QA Contact:	Gossip Maintainers

URL:
Whiteboard:

Duplicates:	353679 (view as bug list)
Depends on:
Blocks:

Reported:	2006-08-09 10:42 UTC by Miguel Rodríguez
Modified:	2006-09-21 20:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Miguel Rodríguez 2006-08-09 10:42:15 UTC

What were you doing when the application crashed?
Loggin into a jabber account.


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

Memory status: size: 38510592 vsize: 0 resident: 38510592 share: 0 rss: 15781888 rss_rlim: 0
CPU usage: start_time: 1155120005 rtime: 0 utime: 91 stime: 0 cutime:82 cstime: 0 timeout: 9 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 -1226856784 (LWP 18675)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 70122

Thread 1 (Thread -1226856784 (LWP 18675))

#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 _lm_connection_succeeded
from /usr/lib/libloudmouth-1.so.0
#5 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#6 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#7 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#8 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#9 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#10 main
#0 __kernel_vsyscall

Comment 1 Richard Hult 2006-08-22 18:48:14 UTC

This only crashes due to warnings => abort in 2.15. Might be the same recent lm crashes we've seen a few times.

Comment 2 Richard Hult 2006-08-22 19:01:25 UTC

This might be a dup, or related to #351665.

Comment 3 Richard Hult 2006-09-09 08:04:54 UTC

*** Bug 353679 has been marked as a duplicate of this bug. ***

Comment 4 Richard Hult 2006-09-09 08:06:28 UTC

Do you use a HTTP proxy?

Comment 5 Miguel Rodríguez 2006-09-11 07:01:33 UTC

No, I don't.

Comment 6 Richard Hult 2006-09-21 20:03:57 UTC

The warning in loudmouth that led to crashes in the unstable gnome 2.15 series is fixed now, so closing this.