Bug 558228 – crash in Terminal:

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 558228 - crash in Terminal:


Summary:	crash in Terminal:


Status:	RESOLVED DUPLICATE of bug 561663

Product:	gnome-terminal
Classification:	Core
Component:	BugBuddyBugs
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-10-28 12:03 UTC by mroedder
Modified:	2008-11-20 12:10 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description mroedder 2008-10-28 12:03:36 UTC

Version: 2.24.1.1

What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.24.1 2008-10-25 (Archlinux)
BugBuddy Version: 2.24.1

System: Linux 2.6.27-ARCH #1 SMP PREEMPT Sun Oct 26 10:36:46 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: (null)
Icon Theme: (null)

Memory status: size: 26583040 vsize: 26583040 resident: 8757248 share: 7184384 rss: 8757248 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225195386 rtime: 3 utime: 2 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6c7faf0 (LWP 6067)]
0xb7fb2424 in __kernel_vsyscall ()

+ Trace 208814

Thread 1 (Thread 0xb6c7faf0 (LWP 6067))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 run_bug_buddy
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 check_if_gdb
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 bugbuddy_segv_handle
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 <signal handler called>
#8 __kernel_vsyscall
#9 raise
from /lib/libc.so.6
#10 abort
from /lib/libc.so.6
#11 g_assertion_message
from /usr/lib/libglib-2.0.so.0
#12 g_assertion_message_expr
from /usr/lib/libglib-2.0.so.0
#13 terminal_app_init
#14 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#15 g_object_constructor
from /usr/lib/libgobject-2.0.so.0
#16 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#17 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_object_new
from /usr/lib/libgobject-2.0.so.0
#19 terminal_app_initialize
#20 main
#0 __kernel_vsyscall

Comment 1 Christian Persch 2008-10-30 00:04:17 UTC

Thanks for taking the time to report this bug.

Could paste the output of 

  grep gnome-terminal ~/.xsession-error 

here? It might at least have the info about which assertion is failing.

Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Christian Persch 2008-11-20 12:10:07 UTC


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