Summary: | akonadiserver has an unhandled protocol exception | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Steve <sgrubb> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bgodusky, dennis.schridde, dvratil, kde, mark, micuintus, mikemol, rdieter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/akonadi/da7070a7facb3c2f91c03b28c36ba5b929b89a42 | Version Fixed In: | 5.6.1 |
Sentry Crash Report: |
Description
Steve
2017-03-15 17:31:00 UTC
Duplicate of bug #374734? I think this is different because its dying via an abort() call. They are usually placed in code to stop a program when its doing something that violates some expectation. The idea is to force a coredump to collect a backtrace to get an idea of what's wrong. At line 8 the code throws a protocol exception and this probably comes near the code mentioned in line 9. So, something unexpected in the imap protocol is probably causing the issue. DrKonqi suggested both bugs, this and duplicates of the other, as possible duplicates of a crash that I was experiencing. I assumed that was because the backtrace was the same. In src/server/connection.cpp at line 404, there should probably be a try/catch around the Protocol::serialize() call: void Connection::sendResponse(qint64 tag, const Protocol::Command &response) { if (Tracer::self()->currentTracer() != QLatin1String("null")) { Tracer::self()->connectionOutput(m_identifier, QByteArray::number(tag) + ' ' + response.debugString().toUtf8()); } QDataStream stream(m_socket); stream << tag; Protocol::serialize(m_socket, response); } because way down at the bottom in src/private/datastream_p_p.h at line 92, we find: if (mDev->write((char *)&val, sizeof(T)) != sizeof(T)) { throw Akonadi::ProtocolException("Failed to write data to stream"); } Does this help? *** Bug 377871 has been marked as a duplicate of this bug. *** Some information printed to the console around the time of another abort: org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 2061954 "" org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 2061955 "" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-sgrubb.jJx32f/akonadiserver-cmd.socket" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed" org.kde.pim.akonadicore: Error on fetching collection statistics: "" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-sgrubb.jJx32f/akonadiserver-cmd.socket" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket" "Unknown error." org.kde.pim.akonadicore: Error on fetching collection statistics: "" "Unknown error." org.kde.pim.akonadicore: Error on fetching collection statistics: "" Git commit da7070a7facb3c2f91c03b28c36ba5b929b89a42 by Daniel Vrátil. Committed on 01/04/2017 at 10:31. Pushed by dvratil into branch 'Applications/17.04'. Handle nested exceptions during error handling FIXED-IN: 5.6.1 M +30 -4 src/server/connection.cpp https://commits.kde.org/akonadi/da7070a7facb3c2f91c03b28c36ba5b929b89a42 *** Bug 378766 has been marked as a duplicate of this bug. *** *** Bug 380394 has been marked as a duplicate of this bug. *** *** Bug 382439 has been marked as a duplicate of this bug. *** *** Bug 389500 has been marked as a duplicate of this bug. *** |