Bug 152567 – Crash, unknown cause

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 152567 - Crash, unknown cause


Summary:	Crash, unknown cause


Status:	VERIFIED INCOMPLETE

Product:	gossip
Classification:	Deprecated
Component:	General
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	0.8
Assigned To:	Gossip Maintainers
QA Contact:	Gossip Maintainers

URL:
Whiteboard:

Depends on:	157841
Blocks:

Reported:	2004-09-14 03:11 UTC by Brian Skahan
Modified:	2009-08-15 18:40 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Brian Skahan 2004-09-14 03:11:30 UTC

Sorry, was in several chatrooms and one individual chat.  Not doing anything
active at the time of crass, gossip windows not focused.

Using gossip CVS from Monday, September 13 2004.  Tabbed chatrooms are great, btw.

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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1088041760 (LWP 3219)]
0x402a940e in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 50124

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_check_instance_cast
from /usr/lib/libgobject-2.0.so.0
#4 group_chat_presence_handler
at gossip-group-chat.c line 913
#5 _lm_message_handler_handle_message
from /usr/lib/libloudmouth-1.so.0
#6 ??
from /usr/lib/libloudmouth-1.so.0
#7 ??
#8 ??
#9 ??
#10 ??
from /usr/lib/libglib-2.0.so.0
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libloudmouth-1.so.0
#15 ??
#16 ??
#17 ??
#18 _lm_connection_failed
from /usr/lib/libloudmouth-1.so.0

Comment 1 Vincent Noel 2004-09-14 14:44:53 UTC

Unique stack trace.

Comment 2 Mikael Hallendal 2005-01-19 22:39:03 UTC

Can you remember if you at any point in your session had been in a chat room and
then left (closed the window/tab)?

Comment 3 Brian Skahan 2005-01-20 04:34:22 UTC

I had several IM windows and 2 MUC chats open.  Was working in a different
application, none of the gossip windows had focus.

Comment 4 Brian Skahan 2005-01-20 04:35:53 UTC

oops, misunderstood question.

> Can you remember if you at any point in your session had been in a chat room 
> and then left (closed the window/tab)?

Sorry, its possible but I don't recall.

Comment 5 Mikael Hallendal 2005-01-20 09:02:09 UTC

OK, I'm going to close this, I fixed two bugs that could both have triggered
this issue. I do think that it's the issue where you left a chat (closed the
window). Gossip for some reason didn't leave the chat but would crash when a new
message came in that chat since the window was destroyed.