Bug 357861 – crash in XChat-GNOME IRC Chat: no user action

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 357861 - crash in XChat-GNOME IRC Chat: no user action


Summary:	crash in XChat-GNOME IRC Chat: no user action


Status:	RESOLVED INCOMPLETE

Product:	xchat-gnome
Classification:	Other
Component:	general
Version:	0.13
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	xchat-gnome maintainers
QA Contact:	xchat-gnome maintainers

URL:
Whiteboard:

Duplicates:	371000 375504 387518 393795 396987 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-26 18:37 UTC by Dominik Zabłotny
Modified:	2007-01-15 19:30 UTC

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

Description Dominik Zabłotny 2006-09-26 18:37:50 UTC

What were you doing when the application crashed?
no user action


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

Memory status: size: 149217280 vsize: 0 resident: 149217280 share: 0 rss: 28123136 rss_rlim: 0
CPU usage: start_time: 1159295633 rtime: 0 utime: 410 stime: 0 cutime:374 cstime: 0 timeout: 36 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/xchat-gnome'

(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 -1226320208 (LWP 15635)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 73333

Thread 1 (Thread -1226320208 (LWP 15635))

#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 g_slist_remove
from /usr/lib/libglib-2.0.so.0
#5 gtk_tree_row_reference_free
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_tree_view_get_path_at_pos
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_tree_view_set_fixed_height_mode
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_tree_view_set_fixed_height_mode
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_tree_view_set_fixed_height_mode
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#15 fe_main
#16 main
#0 __kernel_vsyscall

Comment 1 David Trowbridge 2006-09-30 22:37:03 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 David Trowbridge 2006-10-25 05:50:21 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 3 André Klapper 2006-11-05 14:10:34 UTC

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

Comment 4 Guillaume Desmottes 2006-11-15 13:19:33 UTC

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

Comment 5 David Trowbridge 2006-12-19 22:07:01 UTC

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

Comment 6 David Trowbridge 2007-01-07 04:48:15 UTC

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

Comment 7 David Trowbridge 2007-01-15 19:30:25 UTC

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