Bug 408153 – crash in Terminal: Just running a shell scr...

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 408153 - crash in Terminal: Just running a shell scr...


Summary:	crash in Terminal: Just running a shell scr...


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-02-15 08:11 UTC by rob.kirkbride
Modified:	2007-02-15 18:03 UTC

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

Description rob.kirkbride 2007-02-15 08:11:39 UTC

Version: 2.16.1

What were you doing when the application crashed?
Just running a shell script which was simply scrolling text up the screen


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

Memory status: size: 96743424 vsize: 0 resident: 96743424 share: 0 rss: 59244544 rss_rlim: 0
CPU usage: start_time: 1171438811 rtime: 0 utime: 6546 stime: 0 cutime:5351 cstime: 0 timeout: 1195 it_real_value: 0 frequency: 33295

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 -1226529104 (LWP 28421)]
[New Thread -1248900192 (LWP 28425)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 110908

Thread 1 (Thread -1226529104 (LWP 28421))

#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_region_intersect
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_container_propagate_expose
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_container_propagate_expose
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_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_window_new
from /usr/lib/libgtk-x11-2.0.so.0
#14 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#23 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#24 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#25 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#28 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
#31 ??
#32 _IO_stdin_used
#33 ??
#34 ??
#0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2007-02-15 18:03:34 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 ***