After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 600435 - crash in Terminal: sudo vi /etc/hosts and t...
crash in Terminal: sudo vi /etc/hosts and t...
Status: RESOLVED DUPLICATE of bug 596460
Product: vte
Classification: Core
Component: general
0.22.x
Other All
: Normal critical
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-02 15:25 UTC by nico.behrens
Modified: 2009-11-02 16:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description nico.behrens 2009-11-02 15:25:46 UTC
Version: 2.28.0

What were you doing when the application crashed?
sudo vi /etc/hosts and then a bug report showed up!


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: 161087488 vsize: 161087488 resident: 32215040 share: 0 rss: 32215040 rss_rlim: 0
CPU usage: start_time: 1256545815 rtime: 52853 utime: 378354055 stime: 150182065 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-terminal'

3857:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3e25 waitid   (0, 2df2, 8046fe0, 3)
 feea3305 waitpid  (2df2, 804709c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 8ef9328, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (8e0dfc8, 0, 0, 0, 80471bc) + 5c
 fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, f11, 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 (8e4ef10, 0, 50, fd80f706) + 1f
 fd80f81d vte_sequence_handler_cd (8e4ee08, 0, 80475a8, fd812112) + 125
 fd812178 vte_sequence_handler_erase_in_display (8e4ee08, 8175780, f, fd81376a) + 74
 fd813895 _vte_terminal_handle_sequence (8e4ee08, 81d16b0, 507, 8175780) + 139
 fd7f2d99 vte_terminal_process_incoming (8e4ee08, 0) + 405
 fd80481c time_process_incoming (8e4ee08, 1, 8e4ee08, fd8048ae) + 2c
 fd804a4c process_timeout (0, fedcc460, 8047748, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (89953b0, fd8048a0, 0, 80477c0) + 23
 fed24eee g_main_context_dispatch (80cbe38, 0, 8e54008, a) + 262
 fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483
 fed25bc9 g_main_loop_run (825a978, 825a978, 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, f5caef50, 14)
 fed270c1 child_watch_helper_thread (0, 8254fc8, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (8254fc8, fef81000, f5caefe8, feeee45e) + 133
 feeee4b3 _thrp_setup (fdcb0a00) + 9b
 feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0)


---- Critical and fatal warnings logged during execution ----

** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed 
** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed 
** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed 
** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed 
** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed 


----------- .xsession-errors (630060 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...
--------------------------------------------------
Comment 1 Behdad Esfahbod 2009-11-02 16:27:02 UTC

*** This bug has been marked as a duplicate of bug 596460 ***