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 626012 - crash in Terminal: tried to ssh
crash in Terminal: tried to ssh
Status: RESOLVED DUPLICATE of bug 596460
Product: gnome-terminal
Classification: Core
Component: BugBuddyBugs
2.28.x
Other All
: Normal critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-04 11:31 UTC by Alex
Modified: 2010-08-04 16:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Alex 2010-08-04 11:31:18 UTC
Version: 2.28.0

What were you doing when the application crashed?
tried to ssh


Distribution:                   Solaris Express Community Edition snv_125 X86
Gnome Release: 2.28.0 2009-09-28 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0

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

Memory status: size: 56799232 vsize: 56799232 resident: 24629248 share: 905216 rss: 24629248 rss_rlim: 0
CPU usage: start_time: 1280526984 rtime: 14169 utime: 113168902 stime: 28529983 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

6248:	gnome-terminal --sm-client-id 10d68f4468c79083d01246587520553780000000
-----------------  lwp# 1 / thread# 1  --------------------
 feef3e25 waitid   (0, 3f2a, 8046390, 3)
 feea3305 waitpid  (3f2a, 804644c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 815d0f0, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (84c1a10, 0, 0, 0, 804656c) + 5c
 fdac1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 1868, 0, fdac1ff2) + f3
 fdac20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 80465f4, feeee825, b, 0) + 12e
 fdac1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80466a8, fecc2a00, fef81000, 8046664) + 64
 feeee825 __sighndlr (b, 0, 80466a8, fdac1a30) + 15
 feee15ef call_user_handler (b) + 2af
 feee181f sigacthandler (b, 0, 80466a8) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fd78ce63 _vte_terminal_ring_append (846e908, 0, 87, fd7af706) + 1f
 fd7af81d vte_sequence_handler_cd (846e800, 0, 8046958, fd7b2112) + 125
 fd7b2178 vte_sequence_handler_erase_in_display (846e800, 81667c0, f, fd7b376a) + 74
 fd7b3895 _vte_terminal_handle_sequence (846e800, 80dcdf0, 502, 81667c0) + 139
 fd792d99 vte_terminal_process_incoming (846e800, 0) + 405
 fd7a481c time_process_incoming (846e800, 1, 846e800, fd7a48ae) + 2c
 fd7a4a4c process_timeout (0, fedcc460, 8046af8, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (84f3118, fd7a48a0, 0, 8046b70) + 23
 fed24eee g_main_context_dispatch (80c9b80, 0, 846a008, a) + 262
 fed2559f g_main_context_iterate (80c9b80, 1, 1, 80a6858) + 483
 fed25bc9 g_main_loop_run (82440d8, 82440d8, 80a9800, fe37e73a) + 1dd
 fe37e7e3 gtk_main (3, 0, 80aa9e4, feffb804, 8046d50, fefdcf48) + b7
 0806b594 main     (1, 8046da8, 8046db8, 8046d9c) + 944
 080677fd _start   (3, 8046f1c, 0, 0, 0, 8046f6b) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef35c5 read     (14, fbbeef50, 14)
 fed270c1 child_watch_helper_thread (0, 8237b78, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (8237b78, fef81000, fbbeefe8, feeee45e) + 133
 feeee4b3 _thrp_setup (fdc60a00) + 9b
 feeee740 _lwp_start (fdc60a00, 0, 0, 0, 0, 0)
Comment 1 Behdad Esfahbod 2010-08-04 16:35:26 UTC

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