GNOME Bugzilla – Bug 599439
crash in Terminal: setting term vt220
Last modified: 2009-10-23 19:17:16 UTC
Version: 2.28.0 What were you doing when the application crashed? setting term vt220 Distribution: OpenSolaris Development snv_125 X86 Gnome Release: 2.28.0 2009-09-29 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10603000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 100556800 vsize: 100556800 resident: 23949312 share: 2555904 rss: 23949312 rss_rlim: 0 CPU usage: start_time: 1256259436 rtime: 2650 utime: 22745655 stime: 3761583 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 720: gnome-terminal --sm-client-id 10154a5b4db0662b6a1253828620411216000000 ----------------- lwp# 1 / thread# 1 -------------------- feef3e25 waitid (0, 63b, 8046fe0, 3) feea3305 waitpid (63b, 804709c, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 85c0e70, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (82fde00, 0, 0, 0, 80471bc) + 5c fdb81e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58b8, 2d0, 0, fdb81ff2) + f3 fdb820d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee825, b, 0) + 12e fdb81a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64 feeee825 __sighndlr (b, 0, 80472f8, fdb81a30) + 15 feee15ef call_user_handler (b) + 2af feee181f sigacthandler (b, 0, 80472f8) + df --- called from signal handler with signal 11 (SIGSEGV) --- fd85ce63 _vte_terminal_ring_append (8573908, 0, 50, fd87f706) + 1f fd87f81d vte_sequence_handler_cd (8573800, 0, 80475a8, fd882112) + 125 fd882178 vte_sequence_handler_erase_in_display (8573800, 83b4770, f, fd88376a) + 74 fd883895 _vte_terminal_handle_sequence (8573800, 80d7c88, 506, 83b4770) + 139 fd862d99 vte_terminal_process_incoming (8573800, 0) + 405 fd87481c time_process_incoming (8573800, 1, 8573800, fd8748ae) + 2c fd874a4c process_timeout (0, fedcc460, 8047748, fed26c71) + 1ac fed26c87 g_timeout_dispatch (84e9fb0, fd8748a0, 0, 80477c0) + 23 fed24eee g_main_context_dispatch (80c26a8, 0, 851ef08, 1c) + 262 fed2559f g_main_context_iterate (80c26a8, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (8227148, 8227148, 80a9800, fe37e73a) + 1dd fe37e7e3 gtk_main (3, 0, 80c42c4, feffb804, 80479a0, fefdcf48) + b7 0806b594 main (1, 80479f8, 8047a08, 80479ec) + 944 080677fd _start (3, 8047b0c, 0, 0, 0, 8047b5b) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feef35c5 read (15, f8aeef50, 14) fed270c1 child_watch_helper_thread (0, 8238b60, 200, fed4d1de) + 29 fed4d303 g_thread_create_proxy (8238b60, fef81000, f8aeefe8, feeee45e) + 133 feeee4b3 _thrp_setup (fdcf0a00) + 9b feeee740 _lwp_start (fdcf0a00, 0, 0, 0, 0, 0) ----------- .xsession-errors (63713 sec old) --------------------- (firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
*** This bug has been marked as a duplicate of bug 596460 ***