GNOME Bugzilla – Bug 486383
crash in Tasks:
Last modified: 2007-10-14 13:15:14 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 120250368 vsize: 120250368 resident: 52166656 share: 26460160 rss: 52166656 rss_rlim: 4294967295 CPU usage: start_time: 1192299571 rtime: 202 utime: 185 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208596768 (LWP 20490)] [New Thread -1290130544 (LWP 20508)] [New Thread -1240470640 (LWP 20495)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170004
Thread 1 (Thread -1208596768 (LWP 20490))
----------- .xsession-errors (5725 sec old) --------------------- Done. Increasing itip formatter search count to 1 Increasing itip formatter search count to 2 Decreasing itip formatter search count to 1 Decreasing itip formatter search count to 0 vmware is installed, but it has not been (correctly) configured for this system. To (re-)configure it, invoke the following command: /usr/bin/vmware-config.pl. /usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2) ** WARNING **: Failed to open font: "-adobe-helvetica-bold-r-*-*-10-*". Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3f specified for 0x1405ec7 (). (gnome-terminal:2672): Vte-WARNING **: No handler for control sequence `device-control-string' defined. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing the elements necessary to solve the problem. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 364700 ***