GNOME Bugzilla – Bug 378840
crash in Terminal: Running a simple Java co...
Last modified: 2006-11-24 21:31:12 UTC
Version: 2.16.0 What were you doing when the application crashed? Running a simple Java command line program. 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:2896): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2896): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2896): WARNING **: No handler for control sequence `device-control-string' defined. ** (gnome-terminal:2896): WARNING **: No handler for control sequence `device-control-string' defined. Fri Nov 24 14:07:20 2006 main: End of stream Error: Bad annotation destination (gnome-terminal:2896): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE (style)' failed ** (bug-buddy:12578): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 65634304 vsize: 0 resident: 65634304 share: 0 rss: 16986112 rss_rlim: 0 CPU usage: start_time: 1164363872 rtime: 0 utime: 1003 stime: 0 cutime:781 cstime: 0 timeout: 222 it_real_value: 0 frequency: 7 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 -1208551728 (LWP 2896)] [New Thread -1214555248 (LWP 2901)] (no debugging symbols found) 0x00295402 in __kernel_vsyscall ()
+ Trace 89026
Thread 1 (Thread -1208551728 (LWP 2896))
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 348979 ***