GNOME Bugzilla – Bug 376354
crash in Terminal: right click on the termi...
Last modified: 2006-11-17 16:30:37 UTC
Version: 2.16.0 What were you doing when the application crashed? right click on the terminal to paste some command 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.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors (7 sec old) --------------------- Smart Common Input Method 1.4.4 (gdmsetup:3168): libgnomevfs-WARNING **: Failed to open session DBUS connection: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help) Volume monitoring will not work. (gnome-about-me:3295): -properties-WARNING **: EBookStatus returned 20 calling /usr/bin/userinfo -x libGL warning: 3D driver claims to not support visual 0x4b compiz: water: GL_ARB_fragment_program is missing (gnome-terminal:3226): Gtk-CRITICAL **: _gtk_style_peek_property_value: assertion `GTK_IS_STYLE (style)' failed ** (bug-buddy:6745): WARNING **: 无法为 打开文件夹 载入图标 -------------------------------------------------- Memory status: size: 146866176 vsize: 0 resident: 146866176 share: 0 rss: 19697664 rss_rlim: 0 CPU usage: start_time: 1163778750 rtime: 0 utime: 1424 stime: 0 cutime:1048 cstime: 0 timeout: 376 it_real_value: 0 frequency: 0 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 -1208412464 (LWP 3226)] [New Thread -1253553264 (LWP 3230)] (no debugging symbols found) 0x003d1402 in __kernel_vsyscall ()
+ Trace 87245
Thread 1 (Thread -1208412464 (LWP 3226))
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 353498 ***