Bug 394738 – crash in Terminal: The window had two tabs,...

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 394738 - crash in Terminal: The window had two tabs,...


Summary:	crash in Terminal: The window had two tabs,...


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:

Depends on:
Blocks:

Reported:	2007-01-09 18:50 UTC by gnome
Modified:	2007-01-12 01:25 UTC

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

Description gnome 2007-01-09 18:50:49 UTC

Version: 2.16.1

What were you doing when the application crashed?
The window had two tabs, one with a top running remotely refreshing about every second (active at time of crash), another with an idle command prompt. System running top had a very high system load (~110, Linux 2.4) so data came in quite irregularly.

I was pressing q and then Ctrl-D a couple of times to close the terminal. Window showing top (first, active tab) is still visible after the crash.




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

Memory status: size: 186183680 vsize: 186183680 resident: 24190976 share: 11317248 rss: 24190976 rss_rlim: -1
CPU usage: start_time: 1168342776 rtime: 2653 utime: 2385 stime: 268 cutime:2432 cstime: 1984 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 46936552797872 (LWP 11211)]
[New Thread 1082132816 (LWP 11215)]
0x00002ab040635eef in waitpid () from /lib/libpthread.so.0

+ Trace 100768

Thread 1 (Thread 46936552797872 (LWP 11211))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 874
#2 <signal handler called>
#3 gtk_widget_style_get_valist
from /usr/lib64/libgtk-x11-2.0.so.0
#4 gtk_widget_style_get
from /usr/lib64/libgtk-x11-2.0.so.0
#5 gtk_widget_style_get
from /usr/lib64/libgtk-x11-2.0.so.0
#6 gtk_widget_style_get
from /usr/lib64/libgtk-x11-2.0.so.0
#7 gtk_widget_style_get
from /usr/lib64/libgtk-x11-2.0.so.0
#8 gtk_widget_style_get
from /usr/lib64/libgtk-x11-2.0.so.0
#9 gtk_widget_queue_resize
from /usr/lib64/libgtk-x11-2.0.so.0
#10 gtk_widget_set_usize
from /usr/lib64/libgtk-x11-2.0.so.0
#11 gtk_widget_set_usize
from /usr/lib64/libgtk-x11-2.0.so.0
#12 gtk_box_pack_start_defaults
from /usr/lib64/libgtk-x11-2.0.so.0
#13 gtk_notebook_popup_enable
from /usr/lib64/libgtk-x11-2.0.so.0
#14 gtk_box_pack_start_defaults
from /usr/lib64/libgtk-x11-2.0.so.0
#15 gtk_rc_get_module_dir
from /usr/lib64/libgtk-x11-2.0.so.0
#16 gtk_icon_info_get_type
from /usr/lib64/libgtk-x11-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#20 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#21 ??
#22 __libc_start_main
from /lib/libc.so.6
#23 ??
#24 ??
#25 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 palfrey 2007-01-12 01:25:06 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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