Version: unspecified (using Devel) OS: Linux A fatal error is encountered when launching Kmail. Reproducible: Always Steps to Reproduce: - Launch Kontact and go to Kmail - Kmail main window appears Actual Results: But a pop up error dialogue appears saying: 'Kmail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock.' Expected Results: Kmail should launch properly as it was the case last week. This is a regression. Trunk, Svn Rev 1153123
The lock seems to be held by the maildispatcher agent: :1.57 org.freedesktop.Akonadi.Agent.akonadi_maildispatcher_agent org.freedesktop.Akonadi.MailDispatcherAgent org.kde.akonadi_maildispatcher_agent-5114 org.kde.pim.SpecialCollections MorpHeUz said it happens to him too. krake said he suspects Volker's changes to the collection request job. (I found r1152207, r1152210 and r1152237)
I can confirm that the problem is gone after reverting 4 commits in kdepimlibs/akonadi: svn merge -c-1152237 . svn merge -c-1152207 . svn merge -c-1152240 . svn merge -c-1152210 . Reverting just the first two wasn't enough, and 1152240 is just a cleanup, so it's very probably 1152210.
SVN commit 1154803 by mlaurent: Release lock even if we don't have error (more logical) BUG: 245481 M +3 -1 specialcollectionsrequestjob.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1154803
SVN commit 1154807 by mlaurent: Real fix for 245481 BUG: 245481 M +4 -4 specialcollectionsrequestjob.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1154807
*** Bug 245879 has been marked as a duplicate of this bug. ***
fixed with commits 1154803 and 1154807
It is corrected now. The fatal error pop up dialogue does not appear anymore and Kmail works properly now. Trunk, Svn Rev 1156856