Bug 379514 – crash in Terminal: 窗口最化和关闭终端

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 379514 - crash in Terminal: 窗口最化和关闭终端


Summary:	crash in Terminal: 窗口最化和关闭终端


Status:	RESOLVED DUPLICATE of bug 361117

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-26 17:29 UTC by xzymail
Modified:	2006-11-26 21:04 UTC

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

Description xzymail 2006-11-26 17:29:55 UTC

Version: 2.16.1

What were you doing when the application crashed?
窗口最化和关闭终端


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

Memory status: size: 88522752 vsize: 0 resident: 88522752 share: 0 rss: 17244160 rss_rlim: 0
CPU usage: start_time: 1164560569 rtime: 0 utime: 191 stime: 0 cutime:171 cstime: 0 timeout: 20 it_real_value: 0 frequency: 84

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

(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 -1226365264 (LWP 4434)]
[New Thread -1283044448 (LWP 4440)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 89528

Thread 1 (Thread -1226365264 (LWP 4434))

#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_type_check_instance_is_a
from /usr/lib/libgobject-2.0.so.0
#5 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#6 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#7 _gtk_container_dequeue_resize_handler
from /usr/lib/libgtk-x11-2.0.so.0
#8 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#9 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_widget_hide
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
from /usr/lib/libgobject-2.0.so.0
#24 ??
#25 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#26 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#31 vte_terminal_copy_primary
from /usr/lib/libvte.so.9
#32 _vte_debug_parse_string
from /usr/lib/libvte.so.9
#33 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#35 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#36 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#37 vte_reaper_get
from /usr/lib/libvte.so.9
#38 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#39 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#40 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#41 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#42 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
#44 ??
#45 _IO_stdin_used
#46 ??
#47 ??
#0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2006-11-26 21:04:13 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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