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 563366 - crash in Terminal:
crash in Terminal:
Status: RESOLVED INVALID
Product: gnome-terminal
Classification: Core
Component: BugBuddyBugs
2.24.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 563790 563888 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-12-05 18:58 UTC by Mart Raudsepp
Modified: 2008-12-09 21:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Mart Raudsepp 2008-12-05 18:58:18 UTC
Version: 2.24.2

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.12
Gnome Release: 2.24.2 2008-11-28 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.27-gentoo-r3 #1 SMP Wed Nov 19 11:29:01 EET 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 414695424 vsize: 414695424 resident: 156569600 share: 12779520 rss: 156569600 rss_rlim: 18446744073709551615
CPU usage: start_time: 1228478500 rtime: 33072 utime: 20787 stime: 12285 cutime:7506 cstime: 2017 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f26a1b70770 (LWP 4572)]
[New Thread 0x4240f950 (LWP 4576)]
0x00007f26a0478e9f in __libc_waitpid (pid=13955, stat_loc=0x7fffa9bb3050, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7f26a1b70770 (LWP 4572))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 IA__g_spawn_sync
    at gspawn.c line 382
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #3 bugbuddy_segv_handle
    at gnome-breakpad.cc line 213
  • #4 <signal handler called>
  • #5 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #6 *__GI_abort
    at abort.c line 88
  • #7 IA__g_assertion_message
    at gtestutils.c line 1301
  • #8 IA__g_assertion_message_expr
    at gtestutils.c line 1312
  • #9 notebook_page_removed_cb
    at terminal-tabs-menu.c line 133
  • #10 IA__g_closure_invoke
    at gclosure.c line 767
  • #11 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #13 IA__g_signal_emit
    at gsignal.c line 3034
  • #14 gtk_notebook_remove
    at gtknotebook.c line 3756
  • #15 IA__g_closure_invoke
    at gclosure.c line 767
  • #16 signal_emit_unlocked_R
    at gsignal.c line 3174
  • #17 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #18 IA__g_signal_emit
    at gsignal.c line 3034
  • #19 IA__g_closure_invoke
    at gclosure.c line 767
  • #20 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #22 IA__g_signal_emit
    at gsignal.c line 3034
  • #23 IA__g_closure_invoke
    at gclosure.c line 767
  • #24 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #25 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #26 IA__g_signal_emit_by_name
    at gsignal.c line 3071
  • #27 IA__g_closure_invoke
    at gclosure.c line 767
  • #28 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #29 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #30 IA__g_signal_emit_by_name
    at gsignal.c line 3071
  • #31 vte_reaper_child_watch_cb
    at reaper.c line 98
  • #32 g_child_watch_dispatch
    at gmain.c line 3952
  • #33 IA__g_main_context_dispatch
    at gmain.c line 2144
  • #34 g_main_context_iterate
    at gmain.c line 2778
  • #35 IA__g_main_loop_run
    at gmain.c line 2986
  • #36 IA__gtk_main
    at gtkmain.c line 1200
  • #37 main
    at terminal.c line 1252


----------- .xsession-errors ---------------------
Loading stream: http://static.postimees.ee/banners/ba4933f8f268a2e.swf?clickTAG=http://www.postimees.ee/ads/redirect.php?id=3991__AND__ref=www.postimees.ee
Loading stream: http://static.postimees.ee/banners/ba4917f9f3b773e.swf?clickTAG=http://www.postimees.ee/ads/redirect.php?id=3853__AND__ref=www.postimees.ee
Loading stream: http://static.postimees.ee/banners/ba4937986c5d59f.swf?clickTAG=http://www.postimees.ee/ads/redirect.php?id=1843__AND__ref=www.postimees.ee
Loading stream: http://static.postimees.ee/banners/ba492fea2550b08.swf?clickTAG=http://www.postimees.ee/ads/redirect.php?id=3988__AND__ref=www.postimees.ee
Loading stream: http://static.postimees.ee/banners/ba493791f201e3e.swf?clickTAG=http://www.postimees.ee/ads/redirect.php?id=4033__AND__ref=www.postimees.ee
Loading stream: http://static.postimees.ee/banners/ba492a9d594767f.swf?clickTAG=http://www.postimees.ee/ads/redirect.php?id=3888__AND__ref=www.postimees.ee
Loading stream: http://static.postimees.ee/banners/ba49354333bce2d.swf?clickTAG=http://www.postimees.ee/ads/redirect.php?id=4015__AND__ref=www.postimees.ee
unhandled event 19
Loading stream: http://s.ytimg.com/yt/swf/watch-vfl67812.swf
Loading stream: http://pagead2.googlesyndication.com/pagead/imgad?id=COaVopDw_rPlvwEQ2AUYWjII_cSf1zhzeJc
**
ERROR:terminal-tabs-menu.c:133:free_tab_id: assertion failed: (id >= 0 && id < tabs_id_array->len * 8)
warning: .dynamic section for "/usr/lib/libXi.so.6" is not at the expected address (wrong library or version mismatch?)
41	../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
--------------------------------------------------
Comment 1 Christian Persch 2008-12-05 20:25:31 UTC
Do you have any patches in your g-t package?
Comment 2 Christian Persch 2008-12-05 20:26:22 UTC
Nevermind. Assuming you use the patch from bug 562834 in your package, this is caused by it.
Comment 3 Mart Raudsepp 2008-12-06 05:42:44 UTC
Sorry, didn't actually mean to send off this stacktrace yet. Hit the wrong button after saving the trace, I'll follow-up on 562834 later in the weekend.
Comment 4 Mart Raudsepp 2008-12-09 14:25:51 UTC
*** Bug 563790 has been marked as a duplicate of this bug. ***
Comment 5 Bruno Boaventura 2008-12-09 21:21:47 UTC
*** Bug 563888 has been marked as a duplicate of this bug. ***