| Summary: | Protocol::HelloResponse not correctly parsed, the object is just a Command with type set | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Jure Repinc <jlp> |
| Component: | libakonadi | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | dvratil, freekdekruijf, kde, kdepim-bugs, nikolay.brookstein, shawn.starr, vkrause |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jure Repinc
2016-11-20 21:20:04 UTC
Oh and Akonadi version (as reported by akonadictl) is 5.3.3 which is not on the version list I got the same crash on KMail 16.12.0 with Akonadi 16.12.0. Also occurred while KMail was in the background; I was not interacting with it. [KCrash Handler] #6 std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0x18) at /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5/bits/atomic_base.h:396 #7 QAtomicOps<int>::load<int> (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger<int>::load (this=0x18) at /usr/include/qt5/QtCore/qbasicatomic.h:99 #9 QtPrivate::RefCount::ref (this=0x18) at /usr/include/qt5/QtCore/qrefcount.h:55 #10 0x00007fee950bc2d3 in Akonadi::Protocol::Response::errorMessage() const () at ../../../akonadi-16.12.0/src/private/protocol.cpp:488 #11 0x00007fee9f9f3831 in Akonadi::SessionPrivate::handleCommand (this=0x1fcd930, tag=<optimized out>, cmd=...) at ../../../akonadi-16.12.0/src/core/session.cpp:107 #12 0x00007fee9f9f4538 in Akonadi::Session::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7fee740050b0) at ./moc_session.cpp:117 #13 0x00007feea19b39a9 in QObject::event (this=0x1f63b80, e=<optimized out>) at kernel/qobject.cpp:1263 #14 0x00007feea2268cfc in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x1f63b80, e=0x7fee741ad1c0) at kernel/qapplication.cpp:3799 #15 0x00007feea2270040 in QApplication::notify (this=0x7ffc229d3340, receiver=0x1f63b80, e=0x7fee741ad1c0) at kernel/qapplication.cpp:3556 #16 0x00007feea1987ce8 in QCoreApplication::notifyInternal2 (receiver=0x1f63b80, event=event@entry=0x7fee741ad1c0) at kernel/qcoreapplication.cpp:988 #17 0x00007feea198a3ab in QCoreApplication::sendEvent (event=0x7fee741ad1c0, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #18 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1c1e7a0) at kernel/qcoreapplication.cpp:1649 #19 0x00007feea198a818 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #20 0x00007feea19db0d3 in postEventSourceDispatch (s=0x1c79b20) at kernel/qeventdispatcher_glib.cpp:276 #21 0x00007fee9de59507 in g_main_dispatch (context=0x7fee880016f0) at ../../glib-2.50.2/glib/gmain.c:3203 #22 g_main_context_dispatch (context=context@entry=0x7fee880016f0) at ../../glib-2.50.2/glib/gmain.c:3856 #23 0x00007fee9de59790 in g_main_context_iterate (context=context@entry=0x7fee880016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../glib-2.50.2/glib/gmain.c:3929 #24 0x00007fee9de5983c in g_main_context_iteration (context=0x7fee880016f0, may_block=may_block@entry=1) at ../../glib-2.50.2/glib/gmain.c:3990 #25 0x00007feea19db4df in QEventDispatcherGlib::processEvents (this=0x1cbf510, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x00007feea1985cda in QEventLoop::exec (this=this@entry=0x7ffc229d2c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #27 0x00007feea198e2ec in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #28 0x00007feea1cc0d4c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1633 #29 0x00007feea2268c55 in QApplication::exec () at kernel/qapplication.cpp:2975 #30 0x0000000000403ccb in main (argc=1, argv=0x7ffc229d3578) at ../../kmail-16.12.0/src/main.cpp:161 Moving to libakonadi, this is a generic problem in Protocol (?), looks like the the command is not actually a HelloResponse, despite having the type set to Hello. Possibly the Response bit is not set when sent from the server? *** Bug 373242 has been marked as a duplicate of this bug. *** *** Bug 372170 has been marked as a duplicate of this bug. *** *** Bug 374743 has been marked as a duplicate of this bug. *** *** Bug 377230 has been marked as a duplicate of this bug. *** Should be fixed now that the protocol implementation is autogenerated |