Bug 367650 – crash in Terminal: opening a new terminal w...

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 367650 - crash in Terminal: opening a new terminal w...


Summary:	crash in Terminal: opening a new terminal w...


Status:	RESOLVED DUPLICATE of bug 354477

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:

Depends on:
Blocks:

Reported:	2006-10-30 14:13 UTC by sam
Modified:	2006-10-30 16:21 UTC

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

Description sam 2006-10-30 14:13:30 UTC

Version: 2.16.1

What were you doing when the application crashed?
opening a new terminal window
beryl-manager was running


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

Memory status: size: 104091648 vsize: 0 resident: 104091648 share: 0 rss: 27701248 rss_rlim: 0
CPU usage: start_time: 1162200443 rtime: 0 utime: 4575 stime: 0 cutime:4226 cstime: 0 timeout: 349 it_real_value: 0 frequency: 518

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 -1226086736 (LWP 7260)]
[New Thread -1292031072 (LWP 7270)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 80443

Thread 1 (Thread -1226086736 (LWP 7260))

#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 g_object_ref
from /usr/lib/libgobject-2.0.so.0
#5 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_widget_set_parent
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_notebook_new
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_notebook_insert_page_menu
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_notebook_insert_page
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-10-30 16:21:07 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 354477 ***