Version: 2.28.0

What were you doing when the application crashed?
i was remotely logged onto a mac mini su ing to root and then doing visudo when the bloody terminal died! wtf!!!!


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: SlicknesS-black
Icon Theme: black-white_2-Style
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 100937728 vsize: 100937728 resident: 23523328 share: 3014656 rss: 23523328 rss_rlim: 0
CPU usage: start_time: 1257281303 rtime: 197 utime: 1562604 stime: 408504 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

1668:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3d35 waitid   (0, 1285, 8046fe0, 3)
 feea3305 waitpid  (1285, 804709c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 82ba480, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (8109238, 0, 0, 0, 80471bc) + 5c
 fdb21e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 684, 0, fdb21ff2) + f3
 fdb220d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee735, b, 0) + 12e
 fdb21a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
 feeee735 __sighndlr (b, 0, 80472f8, fdb21a30) + 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 (82b5908, 0, b4, fd80f706) + 1f
 fd80f81d vte_sequence_handler_cd (82b5800, 0, 80475a8, fd812112) + 125
 fd812178 vte_sequence_handler_erase_in_display (82b5800, 82cf510, f, fd81376a) + 74
 fd813895 _vte_terminal_handle_sequence (82b5800, 81c2df0, 50a, 82cf510) + 139
 fd7f2d99 vte_terminal_process_incoming (82b5800, 0) + 405
 fd80481c time_process_incoming (82b5800, 1, 82b5800, fd804c62) + 2c
 fd804dd3 update_repeat_timeout (0, fedcc460, 8047748, fed26c71) + 17f
 fed26c87 g_timeout_dispatch (82affb0, fd804c54, 0, 80477c0) + 23
 fed24eee g_main_context_dispatch (80cfda8, c8, 81d8b30, c) + 262
 fed2559f g_main_context_iterate (80cfda8, 1, 1, 80a6858) + 483
 fed25bc9 g_main_loop_run (823d7c8, 823d7c8, 80a9800, fe37e726) + 1dd
 fe37e7cf gtk_main (fefd4e56, 0, 8100c04, feffb804, 80479a0, fefdcf48) + b7
 0806b594 main     (1, 80479fc, 8047a04, feffb804) + 944
 080677fd _start   (1, 8047b0c, 0, 8047b1b, 8047b62, 8047ba6) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef34d5 read     (15, f8a4ef50, 14)
 fed270c1 child_watch_helper_thread (0, 80b3768, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (80b3768, fef81000, f8a4efe8, feeee36e) + 133
 feeee3c3 _thrp_setup (fdcc0a00) + 9b
 feeee650 _lwp_start (fdcc0a00, 0, 0, 0, 0, 0)


----------- .xsession-errors ---------------------
(nautilus:1119): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed
(nautilus:1119): Gtk-WARNING **: About JDS: missing action About JDS
(nautilus:1119): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD
(nautilus:1119): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed
(nautilus:1119): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed
(nautilus:1119): Gtk-WARNING **: About JDS: missing action About JDS
(gnome-terminal:4721): Gtk-WARNING **: Unable to locate theme engine in module_path: "ubuntulooks",
(bug-buddy:4741): Gtk-WARNING **: Unable to locate theme engine in module_path: "ubuntulooks",
--------------------------------------------------