Summary: | kmail crashed after trying to acquire mailbox lock | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Kai Krakow <kai> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | grave | CC: | Martin |
Priority: | NOR | Keywords: | triaged |
Version: | 4.14.3 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Kai Krakow
2015-02-01 11:49:39 UTC
Thank you for your detailed bug report, Kai. Can you enable full debug with kdebugdialog and then start Kontact / KMail from command line and include relevant output? Thank you, Martin Setting to waiting for information after I received bugzilla rights to do that. Apparently the problem currently does no longer occur. I removed some superfluous akonadi resources, probably left-overs from earlier migrations in previous KDE versions, some were simply empty and non-function, others threw erratic errors about missing or duplicate resources. I'm not sure, but that may have fixed the issue. I wonder why and when those resources have been created or obsoleted by akonadi - I never created those. Akonadi's naming scheme is also not very helpful to find out about this. Currently I'm having a new problem instead: I can no longer suspend schedules from my calendars. I get notified over and over again every few seconds to minutes (very spammy), even for events years back. I had to completely disable the calendar notifier for that reason. At least this doesn't seem to affect kmail/kontact's functionality. Maybe it's related, I'm not sure (could be a result of a locking problem, too, I think). I'll get back to this when I start using kontact again: with its current behavior, kontact is quite useless for me and I've resorted back to using web mail and web calendar and/or Android for my resources (GMail, IMAP-Exchange). 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! |