Bug 387518 – crash in XChat-GNOME IRC Chat: I closed Vim and then XC...

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 387518 - crash in XChat-GNOME IRC Chat: I closed Vim and then XC...


Summary:	crash in XChat-GNOME IRC Chat: I closed Vim and then XC...


Status:	RESOLVED DUPLICATE of bug 357861

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:

Depends on:
Blocks:

Reported:	2006-12-19 13:51 UTC by srgold
Modified:	2006-12-19 22:07 UTC

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

Description srgold 2006-12-19 13:51:35 UTC

What were you doing when the application crashed?
I closed Vim and then XChat crashed.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 83832832 vsize: 0 resident: 83832832 share: 0 rss: 23109632 rss_rlim: 0
CPU usage: start_time: 1166532760 rtime: 0 utime: 772 stime: 0 cutime:730 cstime: 0 timeout: 42 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 -1226570064 (LWP 7428)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 95396

Thread 1 (Thread -1226570064 (LWP 7428))

#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-12-19 22:07:01 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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