Version: 2.28.0

What were you doing when the application crashed?
It was fixed in build 126 ? Apparently not!


Distribution:                        OpenSolaris Development snv_126 X86
Gnome Release: 2.28.0 2009-10-13 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: dark-nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 146747392 vsize: 146747392 resident: 20639744 share: 1724416 rss: 20639744 rss_rlim: 0
CPU usage: start_time: 1257344823 rtime: 18 utime: 142579 stime: 37575 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

3694:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3d35 waitid   (0, e80, 8046fe0, 3)
 feea3305 waitpid  (e80, 804709c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 82809e8, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (8280c88, 0, 0, 0, 80471bc) + 5c
 fdae1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, e6e, 0, fdae1ff2) + f3
 fdae20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee735, b, 0) + 12e
 fdae1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
 feeee735 __sighndlr (b, 0, 80472f8, fdae1a30) + 15
 feee15ef call_user_handler (b) + 2af
 feee181f sigacthandler (b, 0, 80472f8) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fd7ece63 _vte_terminal_ring_append (81d5ae8, 0, 50, fd80f706) + 1f
 fd80f81d vte_sequence_handler_cd (81d59e0, 0, 80475a8, fd812112) + 125
 fd812178 vte_sequence_handler_erase_in_display (81d59e0, 827b3c0, f, fd81376a) + 74
 fd813895 _vte_terminal_handle_sequence (81d59e0, 81d1f28, 507, 827b3c0) + 139
 fd7f2d99 vte_terminal_process_incoming (81d59e0, 0) + 405
 fd80481c time_process_incoming (81d59e0, 1, 81d59e0, fd8048ae) + 2c
 fd804a4c process_timeout (0, fedcc460, 8047748, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (827aab0, fd8048a0, 0, 80477c0) + 23
 fed24eee g_main_context_dispatch (80cbe38, 0, 81ee128, a) + 262
 fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483
 fed25bc9 g_main_loop_run (825a678, 825a678, 80a9800, fe37e726) + 1dd
 fe37e7cf gtk_main (3, 0, 80aa044, feffb804, 80479a0, fefdcf48) + b7
 0806b594 main     (1, 80479f8, 8047a00, 80479ec) + 944
 080677fd _start   (1, 8047b08, 0, 8047b17, 8047b62, 8047ba6) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef34d5 read     (15, f5cbef50, 14)
 fed270c1 child_watch_helper_thread (0, 8254c68, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (8254c68, fef81000, f5cbefe8, feeee36e) + 133
 feeee3c3 _thrp_setup (fdca0a00) + 9b
 feeee650 _lwp_start (fdca0a00, 0, 0, 0, 0, 0)


----------- .xsession-errors ---------------------
** (gnome-panel:3543): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3543): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3543): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3543): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3543): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3543): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3543): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3543): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
--------------------------------------------------