| Summary: | KMail crashes when starting because akonadi does not start up fast enough | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Allan Sandfeld <kde> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | bjoern, dominik, doublewitt, entwanzer, frederic.coiffier, null, reavertm, shahn, shlomif, silver.salonen, winter |
| Priority: | HI | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.9.0 | |
| Sentry Crash Report: | |||
|
Description
Allan Sandfeld
2009-12-11 14:43:14 UTC
It should be noted that after clicking on the message the focus is moved but the message does not appear in the message window. The crash happens when you select another message. If you instead wait 2 minutes the message does appear and no crash happens. This is likely a case where the asynchronous processing can not properly deal with actions taken before it is finished. It might be hard to debug without a crashy akonadiserver, but it might be possible to replicate by just delaying the answer long enough that you can click on another message.. I can reliably reproduce the problem with kmail from KDE SC RC1 on Gentoo, using Qt 4.6.0. I cannot even get KMail to start up properly on Fedora 11 as Akonadiserver tries to start up but hangs on startup and eventually crashes, taking KMail with it. I was able to get KMail to work again by renaming ~/local/share/akonadi" to akonadi-old and starting KMail. I suspect something was hosed in the config, but I don't know what. I also suspect that the problem occurred because I had KMail open when the update was installed. *** Bug 226982 has been marked as a duplicate of this bug. *** *** Bug 232805 has been marked as a duplicate of this bug. *** *** Bug 230247 has been marked as a duplicate of this bug. *** I have a similar problem with KDE 4.5rc2 : KMail stops even if Akonadi Self Test doesn't report any error. When I restore my last KDE Session, KDE restores KMail which launch Akonadi and the Akonadi Self Test which reports no error. But, by clicking Ok on the Akonadi Self Test, it closes KMail (but it seems there is no crash). I don't if there is a link but Akonadi requires a KWallet access to retrieve a password for a resource. I don't know if this delay could explain why KMail stops whereas no Akonadi error is reported. *** Bug 246627 has been marked as a duplicate of this bug. *** *** Bug 246574 has been marked as a duplicate of this bug. *** This is a big problem that I encounter on several systems. First start after logon in kmail fails because of akonadi - but akonadi runs fine later and the second start of kmail always works. I noticed that this does not happen if I start kmail without any other system load. But it does happen as soon as I start several applications in parallel. That makes me believe that the main problem is that akonadi is simply starting up slower than kmail expects it. I'm getting a "KMail encountered a fatal error and will terminate now. The error was: Unknown resource". This bug still exists in kmail-4.5.76-0.svn1196728.1mdv2011.0 on Mandriva Linux Cooker. It makes me completely unable to use kmail. How come it wasn't fixed yet? There has been zero activity on this bug report for three months and it's marked "HI" and "Critical". Please fix this bug already. (In reply to comment #12) > I'm getting a "KMail encountered a fatal error and will terminate now. The > error was: Unknown resource". > > This bug still exists in kmail-4.5.76-0.svn1196728.1mdv2011.0 on Mandriva Linux > Cooker. It makes me completely unable to use kmail. How come it wasn't fixed > yet? There has been zero activity on this bug report for three months and it's > marked "HI" and "Critical". Please fix this bug already. I found a workaround to this bug - what I did was run akonadiserver from a konsole command line and then KMail started without an error. However, now I don't see all my ~/.Mail maildirs, even after I enabled them explicitly in the configuration dialogue. But this seems like a different bug, which I'll report on a new bug. This bug is now fixed. Look at release KDE 4.9 and https://bugs.kde.org/show_bug.cgi?id=124111 |