GNOME Bugzilla – Bug 615863
crash in Terminal: was logging in via ssh
Last modified: 2010-04-15 16:31:55 UTC
Version: 2.28.0 What were you doing when the application crashed? was logging in via ssh Distribution: Solaris Express Community Edition snv_125 X86 Gnome Release: 2.28.0 2009-09-28 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: Mist GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 48640000 vsize: 48640000 resident: 24301568 share: 4157440 rss: 24301568 rss_rlim: 0 CPU usage: start_time: 1271213903 rtime: 1721 utime: 13936506 stime: 3276151 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 11011: gnome-terminal --sm-client-id 10d68f4468c79083d01246587520553780000000 ----------------- lwp# 1 / thread# 1 -------------------- feef3e25 waitid (0, 5973, 80463b0, 3) feea3305 waitpid (5973, 804646c, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 82b2890, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (8269148, 0, 0, 0, 804658c) + 5c fdac1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 2b03, 0, fdac1ff2) + f3 fdac20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046614, feeee825, b, 0) + 12e fdac1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80466c8, fecc2a00, fef81000, 8046684) + 64 feeee825 __sighndlr (b, 0, 80466c8, fdac1a30) + 15 feee15ef call_user_handler (b) + 2af feee181f sigacthandler (b, 0, 80466c8) + df --- called from signal handler with signal 11 (SIGSEGV) --- fd78ce63 _vte_terminal_ring_append (836eac0, 0, 6a, fd7af706) + 1f fd7af81d vte_sequence_handler_cd (836e9b8, 0, 8046978, fd7b2112) + 125 fd7b2178 vte_sequence_handler_erase_in_display (836e9b8, 82e1050, f, fd7b376a) + 74 fd7b3895 _vte_terminal_handle_sequence (836e9b8, 819f2f0, 502, 82e1050) + 139 fd792d99 vte_terminal_process_incoming (836e9b8, 0) + 405 fd7a481c time_process_incoming (836e9b8, 1, 836e9b8, fd7a4c62) + 2c fd7a4dd3 update_repeat_timeout (0, fedcc460, 8046b18, fed26c71) + 17f fed26c87 g_timeout_dispatch (822c0a0, fd7a4c54, 0, 8046b90) + 23 fed24eee g_main_context_dispatch (80c9b80, c8, 82e63d8, 13) + 262 fed2559f g_main_context_iterate (80c9b80, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (8243108, 8243108, 80a9800, fe37e73a) + 1dd fe37e7e3 gtk_main (3, 0, 80e5c54, feffb804, 8046d70, fefdcf48) + b7 0806b594 main (1, 8046dc8, 8046dd8, 8046dbc) + 944 080677fd _start (3, 8046f34, 0, 0, 0, 8046f83) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feef35c5 read (14, fbbcef50, 14) fed270c1 child_watch_helper_thread (0, 821bb50, 200, fed4d1de) + 29 fed4d303 g_thread_create_proxy (821bb50, fef81000, fbbcefe8, feeee45e) + 133 feeee4b3 _thrp_setup (fdc60a00) + 9b feeee740 _lwp_start (fdc60a00, 0, 0, 0, 0, 0)
*** This bug has been marked as a duplicate of bug 596460 ***