Bug 245879

Summary:	Kontact doesn't start with a new and fresh account
Product:	[Applications] kontact	Reporter:	Bjoern Ricks <bjoern.ricks>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	vkrause
Priority:	NOR
Version First Reported In:	enterprise
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Bjoern Ricks 2010-07-27 11:31:21 UTC

Version:           enterprise (using Devel) 
OS:                Linux

I am trying to start kontact in a new and clean account (no existing kde and akonadi folder) and after showing the kontact gui for some seconds I am getting a dialog which says:
"KMail encountered a fatal error and will terminate now.
The error was:
Timeout trying to get lock."

Details from console output:
kontact(747)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying to get lock.
kontact(747)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock: "Timeout trying to get lock."
kontact(747) KMKernel::emergencyExit: "KMail encountered a fatal error and will terminate now.
The error was:
Timeout trying to get lock."

version is http://websvn.kde.org/tags/kdepim/enterprise5.0.20100723.1153624/kdepim/

Reproducible: Always

Comment 1 Volker Krause 2010-07-28 10:44:59 UTC


*** This bug has been marked as a duplicate of bug 245481 ***