GNOME Bugzilla – Bug 607096
crash in Terminal: nothing
Last modified: 2010-01-15 19:15:57 UTC
Version: 2.28.0 What were you doing when the application crashed? nothing 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: 90800128 vsize: 90800128 resident: 26263552 share: 0 rss: 26263552 rss_rlim: 0 CPU usage: start_time: 1262233993 rtime: 62245 utime: 497401780 stime: 125048337 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 6614: gnome-terminal --sm-client-id 10d68f4468c79083d01246587520553780000000 ----------------- lwp# 1 / thread# 1 -------------------- feef3e25 waitid (0, 3896, 80463b0, 3) feea3305 waitpid (3896, 804646c, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 83bd0a0, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (8360060, 0, 0, 0, 804658c) + 5c fdac1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 19d6, 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) --- fd77ce63 _vte_terminal_ring_append (829fdf8, 0, 6a, fd79f706) + 1f fd79f81d vte_sequence_handler_cd (829fc50, 0, 831491c, fd7a2112) + 125 fd7a2178 vte_sequence_handler_erase_in_display (829fc50, 82bf530, f, fd7a376a) + 74 fd7a3895 _vte_terminal_handle_sequence (829fc50, 8197dd0, 501, 82bf530) + 139 fd782d99 vte_terminal_process_incoming (829fc50, 0) + 405 fd79481c time_process_incoming (829fc50, 1, 829fc50, fd7948ae) + 2c fd794a4c process_timeout (0, fedcc460, 8046b18, fed26c71) + 1ac fed26c87 g_timeout_dispatch (844daf0, fd7948a0, 0, 8046b90) + 23 fed24eee g_main_context_dispatch (80c9b80, 0, 82bed00, a) + 262 fed2559f g_main_context_iterate (80c9b80, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (823f438, 823f438, 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, fbbaef50, 14)
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. 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 ***