GNOME Bugzilla – Bug 375623
crash in Terminal: trying to open another t...
Last modified: 2006-11-15 19:23:31 UTC
Version: 2.16.0 What were you doing when the application crashed? trying to open another terminal (Ctrl-Shift-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: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- ** (eggcups:2609): WARNING **: IPP request failed with status 1280 evolution-alarm-notify-Message: Setting timeout for 46678 1163660400 1163613722 evolution-alarm-notify-Message: Thu Nov 16 00:00:00 2006 evolution-alarm-notify-Message: Wed Nov 15 11:02:02 2006 winscard_clnt.c:320:SCardEstablishContextTH() Cannot open public shared file: /var/run/pcscd.pub WARNING:root:Could not open log file - using stderr Xlib: unexpected async reply (sequence 0xd)! WARNING:root:Could not open log file - using stderr (gnome-terminal:2611): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE (style)' failed ** (bug-buddy:2964): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 67989504 vsize: 0 resident: 67989504 share: 0 rss: 14979072 rss_rlim: 0 CPU usage: start_time: 1163613719 rtime: 0 utime: 106 stime: 0 cutime:82 cstime: 0 timeout: 24 it_real_value: 0 frequency: 5 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 -1208277296 (LWP 2611)] [New Thread -1215087728 (LWP 2702)] (no debugging symbols found) 0x00e5f402 in __kernel_vsyscall ()
+ Trace 86733
Thread 1 (Thread -1208277296 (LWP 2611))
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 ***