GNOME Bugzilla – Bug 376302
crash in Terminal: Clicking ,about on a gai...
Last modified: 2006-11-17 20:49:38 UTC
Version: 2.16.0 What were you doing when the application crashed? Clicking ,about on a gaim window 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: No Accessibility: Disabled ----------- .xsession-errors --------------------- ** (gnome-terminal:2625): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2625): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2625): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2625): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2625): WARNING **: No handler for control sequence `device-control-string' defined. (gnome-terminal:2625): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed (gnome-terminal:2625): Gtk-CRITICAL **: _gtk_style_peek_property_value: assertion `GTK_IS_STYLE (style)' failed ** (bug-buddy:30337): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 109469696 vsize: 0 resident: 109469696 share: 0 rss: 26775552 rss_rlim: 0 CPU usage: start_time: 1163482906 rtime: 0 utime: 93246 stime: 0 cutime:83732 cstime: 0 timeout: 9514 it_real_value: 0 frequency: 4499 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 -1208187184 (LWP 2625)] [New Thread -1213863024 (LWP 2630)] (no debugging symbols found) 0x00f0d402 in __kernel_vsyscall ()
+ Trace 87210
Thread 1 (Thread -1208187184 (LWP 2625))
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 372549 ***