Bug 375805 – crash in Terminal:

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 375805 - crash in Terminal:


Summary:	crash in Terminal:


Status:	RESOLVED DUPLICATE of bug 348979

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-11-16 05:23 UTC by konstantin
Modified:	2006-11-16 10:28 UTC

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

Description konstantin 2006-11-16 05:23:49 UTC

Version: 2.16.0

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled
----------- .xsession-errors ---------------------
  Resource id:  0x440034c
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  18
  Minor opcode:  0
  Resource id:  0x440034c
ASSERT: "!icon.isEmpty()" in konq_pixmapprovider.cc (81)
ASSERT: "!icon.isEmpty()" in konq_pixmapprovider.cc (81)
ASSERT: "!icon.isEmpty()" in konq_pixmapprovider.cc (81)
ASSERT: "!icon.isEmpty()" in konq_pixmapprovider.cc (81)
kbuildsycoca running...
Reusing existing ksycoca
(gnome-terminal:2899): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE (style)' failed
** (bug-buddy:6794): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 136019968 vsize: 0 resident: 136019968 share: 0 rss: 19337216 rss_rlim: 0
CPU usage: start_time: 1163596789 rtime: 0 utime: 16668 stime: 0 cutime:14207 cstime: 0 timeout: 2461 it_real_value: 0 frequency: 26

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 -1208842544 (LWP 2899)]
[New Thread -1219949680 (LWP 2967)]
0x00611402 in __kernel_vsyscall ()

+ Trace 86858

Thread 1 (Thread -1208842544 (LWP 2899))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_type_check_is_value_type
from /lib/libgobject-2.0.so.0
#5 g_value_type_compatible
from /lib/libgobject-2.0.so.0
#6 g_object_class_override_property
from /lib/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#8 g_signal_emit
from /lib/libgobject-2.0.so.0
#9 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_rc_get_module_dir
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#19 g_main_context_check
from /lib/libglib-2.0.so.0
#20 g_main_loop_run
from /lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__OBJECT
#23 __libc_start_main
from /lib/libc.so.6
#24 g_cclosure_marshal_VOID__OBJECT
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-16 10:28: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 348979 ***