GNOME Bugzilla – Bug 600229
crash in Terminal: Opening gnome-terminal i...
Last modified: 2009-10-31 16:03:36 UTC
Version: 2.28.0 What were you doing when the application crashed? Opening gnome-terminal immediately after updating OS 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: 145014784 vsize: 145014784 resident: 21037056 share: 2347008 rss: 21037056 rss_rlim: 0 CPU usage: start_time: 1257000683 rtime: 22 utime: 187295 stime: 34797 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 4281: /usr/bin/gnome-terminal -x /bin/sh -c cd '/export/home/zi' && exec $SH ----------------- lwp# 1 / thread# 1 -------------------- feef3287 waitid (0, 10bf, 8047010, 3) feea32f5 waitpid (10bf, 80470cc, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 811f880, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (81250e0, 0, 0, 0, 80471ec) + 5c fdae1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58e8, 10b9, 0, fdae1ff2) + f3 fdae20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047274, feeee715, b, 0) + 12e fdae1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8047328, fecc2a00, fef81000, 80472e4) + 64 feeee715 __sighndlr (b, 0, 8047328, fdae1a30) + 15 feee15df call_user_handler (b) + 2af feee180f sigacthandler (b, 0, 8047328) + df --- called from signal handler with signal 11 (SIGSEGV) --- fd7dce63 _vte_terminal_ring_append (81c68f0, 0, 50, fd7ff706) + 1f fd7ff81d vte_sequence_handler_cd (81c67e8, 0, 80475d8, fd802112) + 125 fd802178 vte_sequence_handler_erase_in_display (81c67e8, 8158ed0, f, fd80376a) + 74 fd803895 _vte_terminal_handle_sequence (81c67e8, 81cd6a8, 507, 8158ed0) + 139 fd7e2d99 vte_terminal_process_incoming (81c67e8, 0) + 405 fd7f481c time_process_incoming (81c67e8, 1, 81c67e8, fd7f48ae) + 2c fd7f4a4c process_timeout (0, fedcc460, 8047778, fed26c71) + 1ac fed26c87 g_timeout_dispatch (8113fd0, fd7f48a0, 0, 80477f0) + 23 fed24eee g_main_context_dispatch (80d1538, 0, 81a77f8, b) + 262 fed2559f g_main_context_iterate (80d1538, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (80a5798, 80a5798, 80a9800, fe37e726) + 1dd fe37e7cf gtk_main (fefd4e56, 0, 810f014, feffb804, 80479d0, fefdcf48) + b7 0806b594 main (1, 8047a2c, 8047a44, feffb804) + 944 080677fd _start (5, 8047b48, 8047b60, 8047b63, 8047b6b, 8047b6e) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feef2db7 read (15, f5caef50, 14) fed270c1 child_watch_helper_thread (0, 80b3708, 200, fed4d1de) + 29 fed4d303 g_thread_create_proxy (80b3708, fef81000, f5caefe8, feeee35e) + 133 feeee3b3 _thrp_setup (fdca0a00) + 9b feeee640 _lwp_start (fdca0a00, 0, 0, 0, 0, 0) ----------- .xsession-errors (13 sec old) --------------------- (nautilus:4172): Gtk-CRITICAL **: file gtknotebook.c: line 6894: assertion `GTK_IS_WIDGET (child)' failed ** (nautilus:4172): CRITICAL **: file nautilus-notebook.c: line 271: assertion `GTK_IS_WIDGET (tab_label)' failed (nautilus:4172): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD (nautilus:4172): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed (nautilus:4172): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed (nautilus:4172): 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). Client shut down the connection owned by im_id(1). Client shut down the connection owned by im_id(1). --------------------------------------------------
*** This bug has been marked as a duplicate of bug 596460 ***