GNOME Bugzilla – Bug 474990
crash in Evolution: Starting evolution... to...
Last modified: 2007-10-07 19:12:23 UTC
Version: 2.12.x What were you doing when the application crashed? Starting evolution... to check email ... and... 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 #17 SMP PREEMPT Fri Sep 7 01:01:37 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: 90935296 vsize: 90935296 resident: 39800832 share: 25870336 rss: 39800832 rss_rlim: 4294967295 CPU usage: start_time: 1189291955 rtime: 273 utime: 235 stime: 38 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 -1247557920 (LWP 19110)] [New Thread -1284289648 (LWP 19122)] [New Thread -1272996976 (LWP 19121)] [New Thread -1264567408 (LWP 19119)] 0xb7fb7410 in __kernel_vsyscall ()
+ Trace 161423
Thread 4 (Thread -1264567408 (LWP 19119))
----------- .xsession-errors (9 sec old) --------------------- Window manager warning: Treating resize request of legacy application 0x400000a (mythfronte) as a fullscreen request Window manager warning: Treating resize request of legacy application 0x3e0000a (mythfronte) as a fullscreen request Warning: more than one line! Warning: more than one line! Warning: more than one line! Warning: more than one line! No running windows found No running windows found Warning: more than one line! Warning: more than one line! No running windows found CalDAV Eplugin starting up ... ** (evolution-2.12:19110): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution-2.12:19110): DEBUG: mailto URL program: evolution Generating profiling data in `eprofile.19110' --------------------------------------------------
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 ***