Bug 369333 – crash in Terminal: ouvrir un nouveau termin...

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 369333 - crash in Terminal: ouvrir un nouveau termin...


Summary:	crash in Terminal: ouvrir un nouveau termin...


Status:	RESOLVED DUPLICATE of bug 353498

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Duplicates:	407442 416626 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-02 10:16 UTC by jeanabayi
Modified:	2007-03-10 18:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description jeanabayi 2006-11-02 10:16:04 UTC

Version: 2.16.1

What were you doing when the application crashed?
ouvrir un nouveau terminal


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 54517760 vsize: 0 resident: 54517760 share: 0 rss: 10596352 rss_rlim: 0
CPU usage: start_time: 1162455297 rtime: 0 utime: 125 stime: 0 cutime:109 cstime: 0 timeout: 16 it_real_value: 0 frequency: 530

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225840976 (LWP 6012)]
[New Thread -1248433248 (LWP 6084)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81820

Thread 1 (Thread -1225840976 (LWP 6012))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_widget_style_get_valist
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_widget_queue_resize
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#11 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 gtk_container_remove
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#0 __kernel_vsyscall

Comment 1 Behdad Esfahbod 2006-11-02 14:15:49 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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

Comment 2 palfrey 2007-02-21 17:49:48 UTC

*** Bug 407442 has been marked as a duplicate of this bug. ***

Comment 3 Susana 2007-03-10 18:03:27 UTC

*** Bug 416626 has been marked as a duplicate of this bug. ***