Bug 430623 – crash in Terminal: Running top, trying to s...

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 430623 - crash in Terminal: Running top, trying to s...


Summary:	crash in Terminal: Running top, trying to s...


Status:	RESOLVED DUPLICATE of bug 348470

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-04-17 11:55 UTC by great_staryu
Modified:	2007-04-26 17:40 UTC

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

Description great_staryu 2007-04-17 11:55:50 UTC

Version: 2.16.1

What were you doing when the application crashed?
Running top, trying to see why there was so much HDD activity


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

Memory status: size: 53178368 vsize: 0 resident: 53178368 share: 0 rss: 15085568 rss_rlim: 0
CPU usage: start_time: 1176810896 rtime: 0 utime: 125 stime: 0 cutime:118 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

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 -1226344784 (LWP 5018)]
[New Thread -1248523360 (LWP 5025)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 128486

Thread 1 (Thread -1226344784 (LWP 5018))

#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 vte_terminal_feed_child_binary
from /usr/lib/libvte.so.9
#5 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#6 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#13 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#14 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#15 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#16 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
#22 ??
#23 _IO_stdin_used
#24 ??
#25 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-04-26 17:40:11 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 348470 ***