It sometimes happens to me that after a few days of using osmo-0.2.10, osmo does not start any more.
The CPU usage goes up to 100% on a 2GHz Notebook and nothing happens, until i kill the process.
Removing the ~/.osmo configuration file makes osmo work again. Losing all your Data is unacceptable for productive use, though.
osmo -c still starts the calendar window, though.
I use the default gentoo linux ebuild (configure --disable-dependency-tracking --without-libsyncml).
Hope someone has an idea how to fix this.
Log in to post a comment.