Bug 425025 – crash in Terminal: did a sudo apt-get and k...

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 425025 - crash in Terminal: did a sudo apt-get and k...


Summary:	crash in Terminal: did a sudo apt-get and k...


Status:	RESOLVED DUPLICATE of bug 361117

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-01 00:10 UTC by me
Modified:	2007-04-26 17:24 UTC

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

Description me 2007-04-01 00:10:52 UTC

Version: 2.16.1

What were you doing when the application crashed?
did a sudo apt-get and kaboom


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

Memory status: size: 98013184 vsize: 0 resident: 98013184 share: 0 rss: 16482304 rss_rlim: 0
CPU usage: start_time: 1175385151 rtime: 0 utime: 224 stime: 0 cutime:197 cstime: 0 timeout: 27 it_real_value: 0 frequency: 2114

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 -1226242384 (LWP 13478)]
[New Thread -1292321888 (LWP 13812)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 123948

Thread 1 (Thread -1226242384 (LWP 13478))

#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_type_check_instance_is_a
from /usr/lib/libgobject-2.0.so.0
#5 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#6 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#7 _gtk_container_dequeue_resize_handler
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_window_new
from /usr/lib/libgtk-x11-2.0.so.0
#9 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#10 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_widget_hide
from /usr/lib/libgtk-x11-2.0.so.0
#17 _gtk_window_unset_focus_and_default
from /usr/lib/libgtk-x11-2.0.so.0
#18 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#19 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_widget_destroy
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_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
#28 ??
#29 _IO_stdin_used
#30 ??
#31 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-04-26 17:24:30 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 361117 ***