Originally posted by Baconmon
View Post
Announcement
Collapse
No announcement yet.
Say Hello To The "KDE Leaks" Team
Collapse
X
-
Originally posted by edgar_wibeau View PostSo I set ~/.config/akonadi/akonadiserverrc -> StartServer=false (defaults to "true")
You are incidentally getting the effect of Akonadi not starting (actually crashing) because you probably have not configured the database connection accordingly.
Originally posted by edgar_wibeau View PostYet now, when I start kmail or kontact, it tries to trigger akonadi, waits for like a minute ... and then fails! When I look at akonadi, it says it couldn't be started.
Providing contradictory rules to a machine will alway result in it failing. See some of the old Star Trek episodes if you want to have fun examples
Originally posted by edgar_wibeau View Postcouldn't there be a StartServer Option like "auto" or "ondemand"?
Only applications that want to access data provided through Akonadi are starting it (if not yet running) as part of establishing a session.
That of course only under the assumption that neither distributor nor system administrator have change that.
Originally posted by edgar_wibeau View PostI think, back in the days (or some predecessor framework) worked just like this.
Cheers,
_
Comment
Comment