Version: 2.28.0

What were you doing when the application crashed?
Started zsh as an ordinary user


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: nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 92811264 vsize: 92811264 resident: 21180416 share: 4751360 rss: 21180416 rss_rlim: 0
CPU usage: start_time: 1257164171 rtime: 25 utime: 214604 stime: 41634 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

11690:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3d35 waitid   (0, 2db3, 8046530, 3)
 feea3305 waitpid  (2db3, 80465ec, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 82a2628, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (82a4130, 0, 0, 0, 804670c) + 5c
 fdfc1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a5978, 2daa, 0, fdfc1ff2) + f3
 fdfc20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046794, feeee735, b, 0) + 12e
 fdfc1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046848, fecc2a00, fef81000, 8046804) + 64
 feeee735 __sighndlr (b, 0, 8046848, fdfc1a30) + 15
 feee15ef call_user_handler (b) + 2af
 feee181f sigacthandler (b, 0, 8046848) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fdcace63 _vte_terminal_ring_append (81cf508, 0, 50, fdccf706) + 1f
 fdccf81d vte_sequence_handler_cd (81cf400, 0, 8046af8, fdcd2112) + 125
 fdcd2178 vte_sequence_handler_erase_in_display (81cf400, 829ef60, f, fdcd376a) + 74
 fdcd3895 _vte_terminal_handle_sequence (81cf400, 81cac78, 512, 829ef60) + 139
 fdcb2d99 vte_terminal_process_incoming (81cf400, 0) + 405
 fdcc481c time_process_incoming (81cf400, 1, 81cf400, fdcc48ae) + 2c
 fdcc4a4c process_timeout (0, fedcc460, 8046c98, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (8297518, fdcc48a0, 0, 8046d10) + 23
 fed24eee g_main_context_dispatch (80cac70, 0, 8290448, b) + 262
 fed2559f g_main_context_iterate (80cac70, 1, 1, 80a6a28) + 483
 fed25bc9 g_main_loop_run (8283188, 8283188, 80a9c00, fe97e726) + 1dd
 fe97e7cf gtk_main (3, 0, 80a98bc, feffb804, 8046ef0, fefdcf48) + b7
 0806b594 main     (1, 8046f48, 8046f50, 8046f3c) + 944
 080677fd _start   (1, 80470c4, 0, 80470d3, 804711d, 8047158) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef34d5 read     (14, f910ef50, 14)
 fed270c1 child_watch_helper_thread (0, 80b3468, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (80b3468, fef81000, f910efe8, feeee36e) + 133
 feeee3c3 _thrp_setup (fe180a00) + 9b
 feeee650 _lwp_start (fe180a00, 0, 0, 0, 0, 0)


----------- .xsession-errors (924466 sec old) ---------------------
(nautilus:12124): Gtk-WARNING **: About JDS: missing action About JDS
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
(nautilus:12124): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD
(nautilus:12124): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed
(nautilus:12124): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed
(nautilus:12124): Gtk-WARNING **: About JDS: missing action About JDS
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
** (gnome-power-manager:12152): WARNING **: ERROR: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the
--------------------------------------------------