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 598458 - crash in Terminal:
crash in Terminal:
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-14 16:24 UTC by sam.cramer
Modified: 2009-10-15 23:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description sam.cramer 2009-10-14 16:24:49 UTC
Version: 2.28.0

What were you doing when the application crashed?



Distribution:                 Solaris Express Community Edition snv_nightly 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: 10603000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 93556736 vsize: 93556736 resident: 20697088 share: 3919872 rss: 20697088 rss_rlim: 0
CPU usage: start_time: 1255537259 rtime: 23 utime: 193541 stime: 38810 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

5227:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3377 waitid   (0, 1476, 8046670, 3)
 feea32f5 waitpid  (1476, 804672c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 82302d8, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (8109460, 0, 0, 0, 804684c) + 5c
 fe0a1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a6060, 146b, 0, fe0a1ff2) + f3
 fe0a20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 80468d4, feeee805, b, 0) + 12e
 fe0a1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046988, fecc2a00, fef81000, 8046944) + 64
 feeee805 __sighndlr (b, 0, 8046988, fe0a1a30) + 15
 feee15df call_user_handler (b) + 2af
 feee180f sigacthandler (b, 0, 8046988) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fdd8ce63 _vte_terminal_ring_append (8189710, 0, 50, fddaf706) + 1f
 fddaf81d vte_sequence_handler_cd (8189608, 0, 8046c38, fddb2112) + 125
 fddb2178 vte_sequence_handler_erase_in_display (8189608, 813ce00, f, fddb376a) + 74
 fddb3895 _vte_terminal_handle_sequence (8189608, 8185fe8, 517, 813ce00) + 139
 fdd92d99 vte_terminal_process_incoming (8189608, 0) + 405
 fdda481c time_process_incoming (8189608, 1, 8189608, fdda48ae) + 2c
 fdda4a4c process_timeout (0, fedcc460, 8046dd8, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (82107c8, fdda48a0, 0, 8046e50) + 23
 fed24eee g_main_context_dispatch (80cf240, 0, 8221e18, b) + 262
 fed2559f g_main_context_iterate (80cf240, 1, 1, 80a6828) + 483
 fed25bc9 g_main_loop_run (822ca68, 822ca68, 80a9800, fe97e73a) + 1dd
 fe97e7e3 gtk_main (3, 0, 80f0d64, feffb804, 8047030, fefdcf48) + b7
 0806b594 main     (1, 8047088, 8047090, 804707c) + 944
 080677fd _start   (1, 80471cc, 0, 80471db, 8047220, 804725b) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef2ea7 read     (14, fb17ef50, 14)
 fed270c1 child_watch_helper_thread (0, 8226fe0, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (8226fe0, fef81000, fb17efe8, feeee44e) + 133
 feeee4a3 _thrp_setup (fe230a00) + 9b
 feeee730 _lwp_start (fe230a00, 0, 0, 0, 0, 0)


----------- .xsession-errors (61139868 sec old) ---------------------
Warning:          No symbols defined for <I7F> (keycode 255)
** Message: Querying Xkb extension
** Message: Xkb extension found
The application 'xfce4-session' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
The application 'xfce-mcs-manager' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
alsa: Mixer attach default error: No such device
The application 'gnome-screensaver' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
--------------------------------------------------
Comment 1 Akhil Laddha 2009-10-15 02:58:57 UTC
*** Bug 598465 has been marked as a duplicate of this bug. ***
Comment 2 Akhil Laddha 2009-10-15 02:59:52 UTC
looks dupe of bug 470408
Comment 3 Christian Persch 2009-10-15 23:05:14 UTC
-> vte

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