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 599450 - crash in Terminal: setting term vt100
crash in Terminal: setting term vt100
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-10-23 21:35 UTC by slava
Modified: 2009-10-23 21:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description slava 2009-10-23 21:35:12 UTC
Version: 2.28.0

What were you doing when the application crashed?
setting term vt100


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: Mist
Icon Theme: Mist
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 106041344 vsize: 106041344 resident: 28356608 share: 2781184 rss: 28356608 rss_rlim: 0
CPU usage: start_time: 1256324963 rtime: 11857 utime: 72304960 stime: 46267831 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

1617:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3e25 waitid   (0, 823, 8047070, 3)
 feea3305 waitpid  (823, 804712c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 87fde88, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (87fbe38, 0, 0, 0, 804724c) + 5c
 fdb81e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 651, 0, fdb81ff2) + f3
 fdb820d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 80472d4, feeee825, b, 0) + 12e
 fdb81a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8047388, fecc2a00, fef81000, 8047344) + 64
 feeee825 __sighndlr (b, 0, 8047388, fdb81a30) + 15
 feee15ef call_user_handler (b) + 2af
 feee181f sigacthandler (b, 0, 8047388) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fd86ce63 _vte_terminal_ring_append (852db10, 0, 50, fd88f706) + 1f
 fd88f81d vte_sequence_handler_cd (852da08, 0, 8047638, fd892112) + 125
 fd892178 vte_sequence_handler_erase_in_display (852da08, 83b8740, f, fd89376a) + 74
 fd893895 _vte_terminal_handle_sequence (852da08, 80d7b30, 506, 83b8740) + 139
 fd872d99 vte_terminal_process_incoming (852da08, 0) + 405
 fd88481c time_process_incoming (852da08, 1, 852da08, fd8848ae) + 2c
 fd884a4c process_timeout (0, fedcc460, 80477d8, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (87fe8b0, fd8848a0, 0, 8047850) + 23
 fed24eee g_main_context_dispatch (80c26a8, 0, 8506f08, 1d) + 262
 fed2559f g_main_context_iterate (80c26a8, 1, 1, 80a6858) + 483
 fed25bc9 g_main_loop_run (8226d80, 8226d80, 80a9800, fe37e73a) + 1dd
 fe37e7e3 gtk_main (feffb804, 0, 80c4314, feffb804, 8047a30, fefdcf48) + b7
 0806b594 main     (1, 8047a84, 8047a8c, 806779f) + 944
 080677fd _start   (1, 8047b8c, 0, 8047b9b, 8047be2, 8047c23) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef35c5 read     (15, f8b1ef50, 14)
 fed270c1 child_watch_helper_thread (0, 8230610, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (8230610, fef81000, f8b1efe8, feeee45e) + 133
 feeee4b3 _thrp_setup (fdcf0a00) + 9b
 feeee740 _lwp_start (fdcf0a00, 0, 0, 0, 0, 0)


----------- .xsession-errors (72531 sec old) ---------------------
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Behdad Esfahbod 2009-10-23 21:40:30 UTC

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