GNOME Bugzilla – Bug 599360
crash in Terminal: Started an app which ass...
Last modified: 2009-10-23 12:40:57 UTC
Version: 2.28.0 What were you doing when the application crashed? Started an app which assumed my terminal was "xterm-xfree86". 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: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 146386944 vsize: 146386944 resident: 22577152 share: 4108288 rss: 22577152 rss_rlim: 0 CPU usage: start_time: 1256252744 rtime: 142 utime: 1145674 stime: 280493 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 1413: gnome-terminal ----------------- lwp# 1 / thread# 1 -------------------- feef3e25 waitid (0, 5cb, 8046f50, 3) feea3305 waitpid (5cb, 804700c, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 81af6b0, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (8233168, 0, 0, 0, 804712c) + 5c fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58d0, 585, 0, fdaf1ff2) + f3 fdaf20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 80471b4, feeee825, b, 0) + 12e fdaf1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8047268, fecc2a00, fef81000, 8047224) + 64 feeee825 __sighndlr (b, 0, 8047268, fdaf1a30) + 15 feee15ef call_user_handler (b) + 2af feee181f sigacthandler (b, 0, 8047268) + df --- called from signal handler with signal 11 (SIGSEGV) --- fd7ece63 _vte_terminal_ring_append (81c8200, 0, 50, fd80f706) + 1f fd80f81d vte_sequence_handler_cd (81c80f8, 0, 8047518, fd812112) + 125 fd812178 vte_sequence_handler_erase_in_display (81c80f8, 82add40, f, fd81376a) + 74 fd813895 _vte_terminal_handle_sequence (81c80f8, 8100c00, 50b, 82add40) + 139 fd7f2d99 vte_terminal_process_incoming (81c80f8, 0) + 405 fd80481c time_process_incoming (81c80f8, 1, 81c80f8, fd804ef6) + 2c fd80509b update_timeout (0, fedcc460, 80476b8, fed26c71) + 1b3 fed26c87 g_timeout_dispatch (8257600, fd804ee8, 0, 8047730) + 23 fed24eee g_main_context_dispatch (80d0cc0, 78, 82a7f90, c) + 262 fed2559f g_main_context_iterate (80d0cc0, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (80a57e0, 80a57e0, 80a9800, fe37e73a) + 1dd fe37e7e3 gtk_main (3, 0, 80aa2cc, feffb804, 8047910, fefdcf48) + b7 0806b594 main (1, 8047968, 8047970, 804795c) + 944 080677fd _start (1, 8047a84, 0, 8047a93, 8047ae6, 8047af3) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feef35c5 read (15, f5d0ef50, 14) fed270c1 child_watch_helper_thread (0, 8257880, 200, fed4d1de) + 29 fed4d303 g_thread_create_proxy (8257880, fef81000, f5d0efe8, feeee45e) + 133 feeee4b3 _thrp_setup (fdcb0a00) + 9b feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0) ----------- .xsession-errors (1711 sec old) --------------------- (firefox-bin:1372): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:1372): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:1372): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:1372): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:1372): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:1372): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:1372): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
*** This bug has been marked as a duplicate of bug 596460 ***