Summary: | Akonadi registration or initialization fails | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Martin L ü c h e m <Heinrich20> |
Component: | server | Assignee: | Volker Krause <vkrause> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kde, kdepim-bugs |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Martin L ü c h e m
2010-06-16 07:54:50 UTC
sorry, I forgot: Which applications crash? KMail, KAdressbook, Akonadi itself, all, some of them and/or in different order. This is KDE 4.4.4. Sorry, I always forget that bugs.kde.org does not list thsi version of KDE please add the backtrace of the crash in this bugreport Hallo Nicolas,
Am Donnerstag, 17. Juni 2010, um 10:47:12 schrieb Nicolas Lécureuil:
> please add the backtrace of the crash in this bugreport
sorry but I cannot add a crash report because sometimes it happens and
somtimes it does not happen. May be it has somthing to do with the
chronological order while starting kde and kmail. If it happens from time to
time the situation is even worse and I absolutely cannot send in meaningful
information.
What I really wonder is, why there is no defined order of starting kde and its
resources and a way to control this. Controlling it does NOT mean that I as a
user have to play around with this but that there is a defined order and this
is described so that I can find a solution or even a hint, whatthe reason
might be.
disillusioned, Martin
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |