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 599616 - crash in Terminal: sigh, I hope someone can...
crash in Terminal: sigh, I hope someone can...
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-26 03:18 UTC by chenl
Modified: 2009-10-26 16:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description chenl 2009-10-26 03:18:37 UTC
Version: 2.28.0

What were you doing when the application crashed?
sigh, I hope someone can read this. I was just switching between different tabs and doing very normal typing in the terminal window. It's very bad. Can anyone point me to the stable version?


Distribution:                   Solaris Express Community Edition snv_126 X86
Gnome Release: 2.28.0 2009-10-12 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 178339840 vsize: 178339840 resident: 28135424 share: 798720 rss: 28135424 rss_rlim: 0
CPU usage: start_time: 1256276428 rtime: 5694 utime: 39579451 stime: 17368079 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

5528:	/usr/bin/gnome-terminal -x /bin/sh -c cd '/home/lc152243' && exec $SHE
-----------------  lwp# 1 / thread# 1  --------------------
 feef3287 waitid   (0, 32c6, 80462a0, 3)
 feea32f5 waitpid  (32c6, 804635c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 83268b8, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (83b8680, 0, 0, 0, 804647c) + 5c
 fdd21e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58e8, 1598, 0, fdd21ff2) + f3
 fdd220d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046504, feeee715, b, 0) + 12e
 fdd21a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80465b8, fecc2a00, fef81000, 8046574) + 64
 feeee715 __sighndlr (b, 0, 80465b8, fdd21a30) + 15
 feee15df call_user_handler (b) + 2af
 feee180f sigacthandler (b, 0, 80465b8) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fda0ce63 _vte_terminal_ring_append (83459e0, 0, 59, fda2f706) + 1f
 fda2f81d vte_sequence_handler_cd (83458d8, 0, 3a, fda32112) + 125
 fda32178 vte_sequence_handler_erase_in_display (83458d8, 8353b30, f, fda3376a) + 74
 fda33895 _vte_terminal_handle_sequence (83458d8, 81d2fb0, 50e, 8353b30) + 139
 fda12d99 vte_terminal_process_incoming (83458d8, 0) + 405
 fda2481c time_process_incoming (83458d8, 1, 83458d8, fda248ae) + 2c
 fda24a4c process_timeout (0, fedcc460, 8046a08, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (82ec1b0, fda248a0, 0, 8046a80) + 23
 fed24eee g_main_context_dispatch (80c6d58, 0, 8544608, b) + 262
 fed2559f g_main_context_iterate (80c6d58, 1, 1, 80a6858) + 483
 fed25bc9 g_main_loop_run (80a5798, 80a5798, 80a8c00, fe57e726) + 1dd
 fe57e7cf gtk_main (8046bc0, 0, 810ef3c, feffb804, 8046c60, fefdcf48) + b7
 0806b594 main     (1, 8046cc0, 8046cd8, 8046c7c) + 944
 080677fd _start   (5, 8046e0c, 8046e24, 8046e27, 8046e2f, 8046e32) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef2db7 read     (15, f4ceef50, 14)
 fed270c1 child_watch_helper_thread (0, 80b39a8, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (80b39a8, fef81000, f4ceefe8, feeee35e) + 133
 feeee3b3 _thrp_setup (fdee0a00) + 9b
 feeee640 _lwp_start (fdee0a00, 0, 0, 0, 0, 0)
Comment 1 Akhil Laddha 2009-10-26 13:11:53 UTC
*** Bug 599625 has been marked as a duplicate of this bug. ***
Comment 2 Christian Persch 2009-10-26 16:28:48 UTC

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