GNOME Bugzilla – Bug 598767
crash in Terminal: Opening a terminal windo...
Last modified: 2009-10-18 09:51:46 UTC
Version: 2.28.0 What were you doing when the application crashed? Opening a terminal window Distribution: OpenSolaris Development snv_125 X86 Gnome Release: 2.28.0 2009-09-29 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10603000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 149368832 vsize: 149368832 resident: 26243072 share: 3612672 rss: 26243072 rss_rlim: 0 CPU usage: start_time: 1255782197 rtime: 1089 utime: 7245471 stime: 3645292 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 3425: gnome-terminal ----------------- lwp# 1 / thread# 1 -------------------- d02f3e25 waitid (0, 10fa, 8047010, 3) d02a3305 waitpid (10fa, 80470cc, 0, d015b60d) + 65 d015ba14 g_spawn_sync (0, 82acd18, 0, 4, 0, 0) + 418 d015be28 g_spawn_command_line_sync (8234b48, 0, 0, 0, 80471ec) + 5c cef21e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, d61, 0, cef21ff2) + f3 cef220d6 __1cMcheck_if_gdb6F_v_ (d0381000, d0381000, 8047274, d02ee825, b, 0) + 12e cef21a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8047328, d00c2a00, d0381000, 80472e4) + 64 d02ee825 __sighndlr (b, 0, 8047328, cef21a30) + 15 d02e15ef call_user_handler (b) + 2af d02e181f sigacthandler (b, 0, 8047328) + df --- called from signal handler with signal 11 (SIGSEGV) --- cec1ce63 _vte_terminal_ring_append (82a8908, 0, 62, cec3f706) + 1f cec3f81d vte_sequence_handler_cd (82a8800, 0, 80475d8, cec42112) + 125 cec42178 vte_sequence_handler_erase_in_display (82a8800, 8264740, f, cec4376a) + 74 cec43895 _vte_terminal_handle_sequence (82a8800, 81c15d0, 50b, 8264740) + 139 cec22d99 vte_terminal_process_incoming (82a8800, 0) + 405 cec3481c time_process_incoming (82a8800, 1, 82a8800, cec348ae) + 2c cec34a4c process_timeout (0, d01cc460, 8047778, d0126c71) + 1ac d0126c87 g_timeout_dispatch (8293db0, cec348a0, 0, 80477f0) + 23 d0124eee g_main_context_dispatch (80d0420, 0, 82a9f10, c) + 262 d012559f g_main_context_iterate (80d0420, 1, 1, 80a6858) + 483 d0125bc9 g_main_loop_run (824c798, 824c798, 80a9800, cf7ae73a) + 1dd cf7ae7e3 gtk_main (d03d5e56, 0, 80aa0f4, d03fc804, 80479d0, d03ddf48) + b7 0806b594 main (1, 8047a2c, 8047a34, d03fc804) + 944 080677fd _start (1, 8047b3c, 0, 8047b4b, 8047b90, 8047bcf) + 7d ----------------- lwp# 2 / thread# 2 -------------------- d02f35c5 read (15, c717ef50, 14) d01270c1 child_watch_helper_thread (0, 824f5c0, 200, d014d1de) + 29 d014d303 g_thread_create_proxy (824f5c0, d0381000, c717efe8, d02ee45e) + 133 d02ee4b3 _thrp_setup (cf0d0a00) + 9b d02ee740 _lwp_start (cf0d0a00, 0, 0, 0, 0, 0) ----------- .xsession-errors (5803 sec old) --------------------- (nautilus:3335): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed (nautilus:3335): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed (nautilus:3335): Gtk-WARNING **: About JDS: missing action About JDS (nautilus:3335): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD (nautilus:3335): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed (nautilus:3335): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed (nautilus:3335): Gtk-WARNING **: About JDS: missing action About JDS ** (gnome-power-manager:3336): 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 --------------------------------------------------
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. *** This bug has been marked as a duplicate of bug 596460 ***