GNOME Bugzilla – Bug 601791
crash in Terminal: again... resizing the bl...
Last modified: 2009-11-13 11:30:24 UTC
Version: 2.28.0 What were you doing when the application crashed? again... resizing the bloody window. 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: 149241856 vsize: 149241856 resident: 22753280 share: 1789952 rss: 22753280 rss_rlim: 0 CPU usage: start_time: 1258100377 rtime: 1533 utime: 12209319 stime: 3126476 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 19375: gnome-terminal --title ECC JumpOff -x ssh -l nbehrens 213.46.228.11 ----------------- lwp# 1 / thread# 1 -------------------- feef3d35 waitid (0, 4fa5, 8046fe0, 3) feea3305 waitpid (4fa5, 804709c, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 8478410, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (8425fb8, 0, 0, 0, 80471bc) + 5c fdae1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58d0, 4baf, 0, fdae1ff2) + f3 fdae20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee735, b, 0) + 12e fdae1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64 feeee735 __sighndlr (b, 0, 80472f8, fdae1a30) + 15 feee15ef call_user_handler (b) + 2af feee181f sigacthandler (b, 0, 80472f8) + df --- called from signal handler with signal 11 (SIGSEGV) --- fd7dce63 _vte_terminal_ring_append (8474710, 0, 52, fd7ff706) + 1f fd7ff81d vte_sequence_handler_cd (8474608, 0, e0000, fd802112) + 125 fd802178 vte_sequence_handler_erase_in_display (8474608, 82f2aa0, f, fd80376a) + 74 fd803895 _vte_terminal_handle_sequence (8474608, 81d1f48, 507, 82f2aa0) + 139 fd7e2d99 vte_terminal_process_incoming (8474608, 0) + 405 fd7f481c time_process_incoming (8474608, 1, 8474608, fd7f4ef6) + 2c fd7f509b update_timeout (0, fedcc460, 8047748, fed26c71) + 1b3 fed26c87 g_timeout_dispatch (8282a70, fd7f4ee8, 0, 80477c0) + 23 fed24eee g_main_context_dispatch (80cbe38, 78, 8375468, a) + 262 fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (80a57b0, 80a57b0, 80a9800, fe37e726) + 1dd fe37e7cf gtk_main (feffb804, 0, 811993c, feffb804, 80479a0, fefdcf48) + b7 0806b594 main (1, 80479f4, 8047a18, 806779f) + 944 080677fd _start (8, 8047b1c, 0, 0, 8047b3f, 8047b42) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feef34d5 read (15, f5caef50, 14) fed270c1 child_watch_helper_thread (0, 8254e40, 200, fed4d1de) + 29 fed4d303 g_thread_create_proxy (8254e40, fef81000, f5caefe8, feeee36e) + 133 feeee3c3 _thrp_setup (fdca0a00) + 9b feeee650 _lwp_start (fdca0a00, 0, 0, 0, 0, 0) ----------- .xsession-errors (182480 sec old) --------------------- ** (gnome-panel:843): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:843): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:843): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:843): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:843): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:843): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed ** (gnome-panel:843): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [ ...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 ***