GNOME Bugzilla – Bug 472463
crash in Evolution: Starting evolution...
Last modified: 2007-10-07 19:11:44 UTC
Version: 2.12.x What were you doing when the application crashed? Starting evolution... Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.2 2007-08-15 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-suspend2-r1Y #13 SMP PREEMPT Sun Aug 26 19:29:41 PDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Smooth Gorilla Icon Theme: Gorilla Memory status: size: 91512832 vsize: 91512832 resident: 40288256 share: 25862144 rss: 40288256 rss_rlim: 4294967295 CPU usage: start_time: 1188633930 rtime: 312 utime: 262 stime: 50 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.12' (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 -1248303392 (LWP 10896)] [New Thread -1286067312 (LWP 10924)] [New Thread -1273717872 (LWP 10923)] [New Thread -1265288304 (LWP 10921)] 0xb7efe410 in __kernel_vsyscall ()
+ Trace 159563
Thread 4 (Thread -1265288304 (LWP 10921))
----------- .xsession-errors (16 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 No running windows found Window manager warning: Treating resize request of legacy application 0x3c0039c (Mandrake [) as a fullscreen request CalDAV Eplugin starting up ... ** (evolution-2.12:10896): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution-2.12:10896): DEBUG: mailto URL program: evolution Generating profiling data in `eprofile.10896' --------------------------------------------------
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 339602 ***