GNOME Bugzilla – Bug 600674
crash in Terminal: starting nano
Last modified: 2009-11-04 13:13:24 UTC
Version: 2.28.0 What were you doing when the application crashed? starting nano 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: 148692992 vsize: 148692992 resident: 22581248 share: 2949120 rss: 22581248 rss_rlim: 0 CPU usage: start_time: 1257336502 rtime: 312 utime: 2477888 stime: 650679 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 15490: gnome-terminal --title ECC JumpOff -x ssh -l nbehrens 213.46.228.11 ----------------- lwp# 1 / thread# 1 -------------------- feef3e25 waitid (0, 3de3, 8046fe0, 3) feea3305 waitpid (3de3, 804709c, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 83c2870, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (82e1280, 0, 0, 0, 80471bc) + 5c fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58d0, 3c82, 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) --- fd7ece63 _vte_terminal_ring_append (83c0508, 0, 50, fd80f706) + 1f fd80f81d vte_sequence_handler_cd (83c0400, 0, 80475a8, fd812112) + 125 fd812178 vte_sequence_handler_erase_in_display (83c0400, 827fc50, f, fd81376a) + 74 fd813895 _vte_terminal_handle_sequence (83c0400, 81d26d0, 507, 827fc50) + 139 fd7f2d99 vte_terminal_process_incoming (83c0400, 0) + 405 fd80481c time_process_incoming (83c0400, 1, 83c0400, fd8048ae) + 2c fd804a4c process_timeout (0, fedcc460, 8047748, fed26c71) + 1ac fed26c87 g_timeout_dispatch (82a42c8, fd8048a0, 0, 80477c0) + 23 fed24eee g_main_context_dispatch (80cbe38, 0, 8377580, a) + 262 fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (80a57b0, 80a57b0, 80a9800, fe37e73a) + 1dd fe37e7e3 gtk_main (feffb804, 0, 811e8bc, feffb804, 80479a0, fefdcf48) + b7 0806b594 main (1, 80479f4, 8047a18, 806779f) + 944 080677fd _start (8, 8047b1c, 0, 0, 8047b3f, 8047b42) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feef35c5 read (15, f5caef50, 14) fed270c1 child_watch_helper_thread (0, 8254a28, 200, fed4d1de) + 29 fed4d303 g_thread_create_proxy (8254a28, fef81000, f5caefe8, feeee45e) + 133 feeee4b3 _thrp_setup (fdcb0a00) + 9b feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0) ----------- .xsession-errors (130236 sec old) --------------------- ** (gnome-panel:835): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:835): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:835): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:835): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:835): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:835): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:835): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_sc ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 596460 ***