GNOME Bugzilla – Bug 599625
crash in Terminal: vi .bashrc
Last modified: 2009-10-26 16:28:52 UTC
Version: 2.28.0 What were you doing when the application crashed? vi .bashrc 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: dark-nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 146829312 vsize: 146829312 resident: 20668416 share: 1675264 rss: 20668416 rss_rlim: 0 CPU usage: start_time: 1256545799 rtime: 19 utime: 153099 stime: 40474 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 3776: gnome-terminal ----------------- lwp# 1 / thread# 1 -------------------- feef3e25 waitid (0, f08, 8046fe0, 3) feea3305 waitpid (f08, 804709c, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 82948d8, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (8266700, 0, 0, 0, 80471bc) + 5c fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, ec0, 0, fdaf1ff2) + f3 fdaf20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee825, b, 0) + 12e fdaf1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64 feeee825 __sighndlr (b, 0, 80472f8, fdaf1a30) + 15 feee15ef call_user_handler (b) + 2af feee181f sigacthandler (b, 0, 80472f8) + df --- called from signal handler with signal 11 (SIGSEGV) --- fd7fce63 _vte_terminal_ring_append (81d4ce0, 0, 50, fd81f706) + 1f fd81f81d vte_sequence_handler_cd (81d4bd8, 0, 80475a8, fd822112) + 125 fd822178 vte_sequence_handler_erase_in_display (81d4bd8, 82901c0, f, fd82376a) + 74 fd823895 _vte_terminal_handle_sequence (81d4bd8, 81d16b0, 507, 82901c0) + 139 fd802d99 vte_terminal_process_incoming (81d4bd8, 0) + 405 fd81481c time_process_incoming (81d4bd8, 1, 81d4bd8, fd814ef6) + 2c fd81509b update_timeout (0, fedcc460, 8047748, fed26c71) + 1b3 fed26c87 g_timeout_dispatch (8114e70, fd814ee8, 0, 80477c0) + 23 fed24eee g_main_context_dispatch (80cbe38, 78, 8113048, a) + 262 fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (825a508, 825a508, 80a9800, fe37e73a) + 1dd fe37e7e3 gtk_main (fefd4e56, 0, 80aa0f4, feffb804, 80479a0, fefdcf48) + b7 0806b594 main (1, 80479fc, 8047a04, feffb804) + 944 080677fd _start (1, 8047b0c, 0, 8047b1b, 8047b63, 8047ba7) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feef35c5 read (15, f5cbef50, 14) fed270c1 child_watch_helper_thread (0, 8254b58, 200, fed4d1de) + 29 fed4d303 g_thread_create_proxy (8254b58, fef81000, f5cbefe8, feeee45e) + 133 feeee4b3 _thrp_setup (fdcb0a00) + 9b feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0) ----------- .xsession-errors (331 sec old) --------------------- ** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 & ...Too much output, ignoring rest... --------------------------------------------------
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 599616 ***
*** This bug has been marked as a duplicate of bug 596460 ***