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 601429 - crash in Terminal: I want to start in gnome...
crash in Terminal: I want to start in gnome...
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: 2009-11-10 18:29 UTC by groups
Modified: 2009-11-10 19:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description groups 2009-11-10 18:29:23 UTC
Version: 2.28.0

What were you doing when the application crashed?
I want to start in gnome-terminal ZSH


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: 149168128 vsize: 149168128 resident: 22097920 share: 3411968 rss: 22097920 rss_rlim: 0
CPU usage: start_time: 1257877689 rtime: 18 utime: 149413 stime: 34239 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

2667:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3d35 waitid   (0, a7a, 80467c0, 3)
 feea3305 waitpid  (a7a, 804687c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 825e258, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (8261f00, 0, 0, 0, 804699c) + 5c
 fda21e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a5948, a6b, 0, fda21ff2) + f3
 fda220d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046a24, feeee735, b, 0) + 12e
 fda21a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046ad8, fecc2a00, fef81000, 8046a94) + 64
 feeee735 __sighndlr (b, 0, 8046ad8, fda21a30) + 15
 feee15ef call_user_handler (b) + 2af
 feee181f sigacthandler (b, 0, 8046ad8) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fd70ce63 _vte_terminal_ring_append (81d20f8, 0, 50, fd72f706) + 1f
 fd72f81d vte_sequence_handler_cd (81d1ff0, 0, 8046d88, fd732112) + 125
 fd732178 vte_sequence_handler_erase_in_display (81d1ff0, 8284750, f, fd73376a) + 74
 fd733895 _vte_terminal_handle_sequence (81d1ff0, 81cf518, 50c, 8284750) + 139
 fd712d99 vte_terminal_process_incoming (81d1ff0, 0) + 405
 fd72481c time_process_incoming (81d1ff0, 1, 81d1ff0, fd7248ae) + 2c
 fd724a4c process_timeout (0, fedcc460, 8046f28, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (82846a8, fd7248a0, 0, 8046fa0) + 23
 fed24eee g_main_context_dispatch (80d1100, 0, 825a990, b) + 262
 fed2559f g_main_context_iterate (80d1100, 1, 1, 80a6a28) + 483
 fed25bc9 g_main_loop_run (80a5858, 80a5858, 80a9c00, fe37e726) + 1dd
 fe37e7cf gtk_main (80470e0, 0, 80aa594, feffb804, 8047180, fefdcf48) + b7
 0806b594 main     (1, 80471e0, 80471e8, 804719c) + 944
 080677fd _start   (1, 8047320, 0, 804732f, 8047363, 8047387) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef34d5 read     (15, f7d1df50, 14)
 fed270c1 child_watch_helper_thread (0, 80b39e0, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (80b39e0, fef81000, f7d1dfe8, feeee36e) + 133
 feeee3c3 _thrp_setup (fdbe0a00) + 9b
 feeee650 _lwp_start (fdbe0a00, 0, 0, 0, 0, 0)
Comment 1 Behdad Esfahbod 2009-11-10 19:46:03 UTC

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