GNOME Bugzilla – Bug 387098
crash in Terminal: I think I minimised the ...
Last modified: 2006-12-18 18:38:11 UTC
Version: 2.16.0 What were you doing when the application crashed? I think I minimised the Terminal. This is a 1 day old installation on a new laptop, think I installed libsexy via yum earlier as a dep of some python stuff, without rebooting, could it have confused my gtk libs? 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 --------------------- Done. Input Filename : /usr/share/amsn/skins/default/sounds/type.wav Sample Size : 16-bits Sample Encoding: signed (2's complement) Channels : 1 Sample Rate : 11025 Time: 00:00.74 [00:00.67] of 00:01.41 ( 52.7%) Output Buffer: 35.52K Time: 00:01.41 [00:00.00] of 00:01.41 ( 100.0%) Output Buffer: 67.58K Done. (gnome-terminal:3162): Gtk-CRITICAL **: _gtk_style_peek_property_value: assertion `GTK_IS_STYLE (style)' failed ** (bug-buddy:25685): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 90238976 vsize: 0 resident: 90238976 share: 0 rss: 22151168 rss_rlim: 0 CPU usage: start_time: 1166421531 rtime: 0 utime: 3955 stime: 0 cutime:3262 cstime: 0 timeout: 693 it_real_value: 0 frequency: 6938 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 -1208740144 (LWP 3162)] [New Thread -1215591536 (LWP 3168)] (no debugging symbols found) 0x00f2c402 in __kernel_vsyscall ()
+ Trace 95082
Thread 1 (Thread -1208740144 (LWP 3162))
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 ***