Bug 509956 – 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 509956 - crash in Terminal:


Summary:	crash in Terminal:


Status:	RESOLVED DUPLICATE of bug 499797

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.18.x
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-01-16 17:57 UTC by teste
Modified:	2008-01-24 02:52 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description teste 2008-01-16 17:57:16 UTC

Version: 2.18.0

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 86274048 vsize: 86274048 resident: 19877888 share: 12357632 rss: 19877888 rss_rlim: 4294967295
CPU usage: start_time: 1200505822 rtime: 331 utime: 133 stime: 198 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208162064 (LWP 2937)]
[New Thread -1214407792 (LWP 2941)]
(no debugging symbols found)
0x0073c402 in __kernel_vsyscall ()

+ Trace 185594

Thread 1 (Thread -1208162064 (LWP 2937))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 terminal_profile_update
#5 ??
#6 g_cclosure_marshal_VOID
from /lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /lib/libgobject-2.0.so.0
#8 ??
from /lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#10 g_signal_emit
from /lib/libgobject-2.0.so.0
#11 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#21 ??
from /lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /lib/libgobject-2.0.so.0
#23 ??
from /lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#25 g_signal_emit
from /lib/libgobject-2.0.so.0
#26 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /lib/libgobject-2.0.so.0
#31 ??
from /lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#33 g_signal_emit
from /lib/libgobject-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgdk-x11-2.0.so.0
#38 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#39 ??
from /lib/libglib-2.0.so.0
#40 g_main_loop_run
from /lib/libglib-2.0.so.0
#41 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#42 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
localuser:luiz being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2722
** (gnome-terminal:2937): CRITICAL **: terminal_profile_new: assertion `terminal_profile_lookup (name) == NULL' failed
--------------------------------------------------

Comment 1 André Klapper 2008-01-24 02:52:34 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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