GNOME Bugzilla – Bug 599898
crash in Terminal: started ssh session
Last modified: 2009-10-28 12:43:50 UTC
Version: 2.28.0 What were you doing when the application crashed? started ssh session Distribution: Solaris Express Community Edition snv_126 X86 Gnome Release: 2.28.0 2009-10-12 (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: 49418240 vsize: 49418240 resident: 24920064 share: 4243456 rss: 24920064 rss_rlim: 0 CPU usage: start_time: 1256527382 rtime: 5919 utime: 47513986 stime: 11676256 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 6707: gnome-terminal --sm-client-id 10d68f4468c79083d01246587520553780000000 ----------------- lwp# 1 / thread# 1 -------------------- feef3d35 waitid (0, 6871, 80463b0, 3) feea3305 waitpid (6871, 804646c, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 822cf38, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (83ffa30, 0, 0, 0, 804658c) + 5c fdac1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 1a33, 0, fdac1ff2) + f3 fdac20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046614, feeee735, b, 0) + 12e fdac1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80466c8, fecc2a00, fef81000, 8046684) + 64 feeee735 __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 (83ac0c8, 0, 6a, fd7af706) + 1f fd7af81d vte_sequence_handler_cd (83abfc0, 0, 8046978, fd7b2112) + 125 fd7b2178 vte_sequence_handler_erase_in_display (83abfc0, 82c4850, f, fd7b376a) + 74 fd7b3895 _vte_terminal_handle_sequence (83abfc0, 8197dd0, 501, 82c4850) + 139 fd792d99 vte_terminal_process_incoming (83abfc0, 0) + 405 fd7a481c time_process_incoming (83abfc0, 1, 83abfc0, fd7a48ae) + 2c fd7a4a4c process_timeout (0, fedcc460, 8046b18, fed26c71) + 1ac fed26c87 g_timeout_dispatch (8276b00, fd7a48a0, 0, 8046b90) + 23 fed24eee g_main_context_dispatch (80c9b80, 0, 82fa908, a) + 262 fed2559f g_main_context_iterate (80c9b80, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (823f3d8, 823f3d8, 80a9800, fe37e726) + 1dd fe37e7cf 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 -------------------- feef34d5 read (14, fbbcef50, 14) fed270c1 child_watch_helper_thread (0, 82479b8, 200, fed4d1de) + 29 fed4d303 g_thread_create_proxy (82479b8, fef81000, fbbcefe8, feeee36e) + 133 feeee3c3 _thrp_setup (fdc60a00) + 9b feeee650 _lwp_start (fdc60a00, 0, 0, 0, 0, 0)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 596460 ***