GNOME Bugzilla – Bug 377617
crash in Terminal: Trying to open a new tab...
Last modified: 2006-11-21 17:21:52 UTC
Version: 2.16.0 What were you doing when the application crashed? Trying to open a new tab with Control-T 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 --------------------- ** (gnome-terminal:3217): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:3217): WARNING **: No handler for control sequence `device-control-string' defined. ** Message: <information> You are now connected to the wireless network 'DruryHotels'. (gnome-terminal:3217): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed (gnome-terminal:3217): GLib-GObject-CRITICAL **: g_object_unref: assertion `object->ref_count > 0' failed (gnome-terminal:3217): GLib-GObject-CRITICAL **: g_object_unref: assertion `object->ref_count > 0' failed (gnome-terminal:3217): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE (style)' failed ** (bug-buddy:18188): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 109694976 vsize: 0 resident: 109694976 share: 0 rss: 19664896 rss_rlim: 0 CPU usage: start_time: 1164050682 rtime: 0 utime: 5392 stime: 0 cutime:4642 cstime: 0 timeout: 750 it_real_value: 0 frequency: 16142 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 -1209002288 (LWP 3217)] [New Thread -1215956080 (LWP 3221)] (no debugging symbols found) 0x00873402 in __kernel_vsyscall ()
+ Trace 88125
Thread 1 (Thread -1209002288 (LWP 3217))
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 ***