Summary: | Random crashes of the imap resource | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Christophe Marin <christophe> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | daniel, dvratil |
Priority: | NOR | ||
Version: | GIT (master) | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christophe Marin
2015-09-03 10:26:05 UTC
Same crash today in the indexing agent after restarting it in akonadiconsole : 11:13:55 - akonadi_indexing_agent(18160) - : Invalid command, the world is going to end! 11:13:55 - akonadi_indexing_agent(18160) - : QIODevice::read (QLocalSocket): device not open 11:13:55 - akonadi_indexing_agent(18160) - Akonadi::ConnectionThread::doReconnect: connectToServer "/tmp/akonadi-krop.tXn1wQ/akonadiserver.socket" 11:13:55 - Akonadi(17245) - DebugPrivate::stream: Database "akonadi" opened using driver "QPSQL" 11:13:55 - akonadi_indexing_agent(18160) - : ASSERT: "false" in file /kde/src/5/akonadiserver/src/private/protocol.cpp, line 143 11:13:55 - Akonadi(17244) - : ProcessControl: Application /kde/inst/5/master/bin/akonadi_indexing_agent stopped unexpectedly ( "Process crashed" ) 11:13:55 - Akonadi(17244) - : Application '/kde/inst/5/master/bin/akonadi_indexing_agent' crashed. No restart! 11:13:55 - Akonadi(17245) - DebugPrivate::stream: void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "akonadi_indexing_agent_18160_QuozQH" now serving: () According to Volker there is a bug in Qt which causes that QIODevice::waitForReadyRead() sometimes does not get the notification from Qt internals that there are more data available in the socket, so the function times out and triggers our error handling code. He told me they were trying to hunt the issue down long time ago but failed, mostly because it is extremely difficult to reproduce it - it just happens sometimes, but it's probably not possible to reproduce it manually, or at least not reliably enough to investigate. This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input. |