On initial boot I get an error message that the OS has crashed due to Evolution-Calendar having maxed out the CPU (99%). I don't use it so can I just do a complete removal? I don't use Thunderbird either if they are related.
On initial boot I get an error message that the OS has crashed due to Evolution-Calendar having maxed out the CPU (99%). I don't use it so can I just do a complete removal? I don't use Thunderbird either if they are related.
Evolution Calendar shouldn't be installed by default, but I do see an evolution data server package in synaptic which appears to be a dependency.
"Our intention creates our reality. "
Ubuntu Documentation Search: Popular Pages
Ubuntu: Security Basics
Ubuntu: Flavors
I did a clean install of 12.10 last night and didn't directly install it so I don't know how it got on my system. At any rate I found instructions for removing it but was advised to keep 2 specific evolution files having to do with data server. I no longer have the date and time in my title bar but I'll take that for an uneventful logon.
I seem to have a similar issue with Evolution-Calendar... I had it using 99.9% of CPU usage (according to "Top" in the terminal) at ALL times until I decided to remove anything related to evolution, I have no clock on my OS Status bar ever since...
My hardware is a Thinkpad T500 (Core2 Duo T9400, 2 gigs of ram and radeon HD3650 with open source drivers)
This was a clean install and it seems that the bug only appears on the 64bit version of Ubuntu, as I had tried the 32bit version and did not have this issue.
I get constant 'Sorry Ubuntu has experiencd an internal error' messages. Core i5 ASUS u63jc with 12.10 64bit (8GB RAM).
The culprit appears to be '/usr/lib/evolution-calendar-factory' of package evolution-data-server 3.6.0-ubuntu3 Title: Evolution0calendar-factory crashed with SIGABRT
Last edited by samjury; November 7th, 2012 at 05:49 AM. Reason: more detail
No issues on boot up this morning. Even the mouse didn't freeze which I normally have had to do a hard reset at least once start up. One other thing, which is a new issue since I erased Evolution, is my screen times out even with the setting on Never. But again this along with the missing clock and date from the title line are minor compared with what I had going on before.
My system is finally working properly. Was as easy to fix as uninstalling the "Evolution" packages using synaptic, rebooting and reinstalling afterwards.
They now work fine and the crash/high CPU usage issue is gone.
Also make sure to verify that the package indicator-datetime is reinstalled or your date/time on the title bar will not reappear. If it is missing after uninstalling and reinstalling Evolution packages, simply use this command sudo apt-get install indicator-datetime
Now this thread is really "Solved"! I just figured I would have to do without the clock in the title bar.
It makes no sense to me that uninstalling and reinstalling Evolution would do the trick. It's also interesting that after reinstalling Evolution I was missing the indicator-dateline which was the whole reason I was even going to reinstall. Care to share your logic? BTW, you should post this solution to Launchpad.
Last edited by unibroker; November 7th, 2012 at 04:52 PM. Reason: Launchpad
The only logical explanation I would have for this particular case is that the packages were probably "broken" during the initial Ubuntu install, maybe corrupted files on the ISO, can't say for sure.
I'm also not convinced that this is considered an actual "fix" as it is a way around an existing problem. I will wait before posting to Launchpad, or if I do, I will tag it as a temporary "Band-Aid" solution to a problem during initial installation.
Glad it helped you!
I am having the same problem and was about to uninstall / reinstall but once I saw all the dependent packages that were going to be removed I stopped.
I am using the gnome-fallback and a bunch of packages would cripple the system if I remove them.
I had to go to the fallback to begin with due to so many issues with 12.10 on my netbook.
I guess I need to wait a little longer for a fix.
Thanks for the info here though.
Bookmarks