GNOME Bugzilla – Bug 390590
crash in Terminal: Starting Terminal from t...
Last modified: 2006-12-29 07:13:58 UTC
Version: 2.16.0 What were you doing when the application crashed? Starting Terminal from the toolbar. 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.2868.fc6 #1 SMP Fri Dec 15 17:32:54 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- (gnome-terminal:3500): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE (style)' failed (gnome-terminal:3500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-terminal:3500): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (gnome-terminal:3500): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (gnome-terminal:3500): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (gnome-terminal:3500): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (gnome-terminal:3500): Gtk-CRITICAL **: _gtk_style_peek_property_value: assertion `GTK_IS_STYLE (style)' failed ** (bug-buddy:12719): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 70221824 vsize: 0 resident: 70221824 share: 0 rss: 19771392 rss_rlim: 0 CPU usage: start_time: 1167252725 rtime: 0 utime: 5272 stime: 0 cutime:4489 cstime: 0 timeout: 783 it_real_value: 0 frequency: 34924 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 -1208584496 (LWP 3500)] [New Thread -1215439984 (LWP 3504)] (no debugging symbols found) 0x00bfd402 in __kernel_vsyscall ()
+ Trace 97724
Thread 1 (Thread -1208584496 (LWP 3500))
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 374813 ***