| Summary: | reply to a message crashes kmail | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Michi <woskimi> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | dmitry.a.kuzmenko, montel |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Michi
2015-01-13 22:07:14 UTC
Hi This version is not release yet and will not release in 2015 perhaps in 2016. So it's really not Hi This version is not release yet and will not release in 2015 perhaps in 2016. So it's really not a good idea to use it. But if you use please add full debug package so I will able to debug it. Thanks is that better? [KCrash Handler] #5 0x00007f3184e39968 in main_arena () at /lib64/libc.so.6 #6 0x00007f318771e951 in KLocale::formatDate(QDate const&, KLocale::DateFormat) const () at /usr/lib64/libKF5KDELibs4Support.so.5 #7 0x00007f30f3477363 in TemplateParser::TemplateParser::processWithTemplate(QString const&) (this=0x7fffe1c05480, tmpl=...) at /usr/src/debug/kdepim-4.99.40/templateparser/templateparser.cpp:1041 #8 0x00007f30f3469214 in TemplateParser::TemplateParser::process(boost::shared_ptr<KMime::Message> const&, Akonadi::Collection const&) (this=this@entry=0x7fffe1c05480, aorig_msg=..., afolder=...) at /usr/src/debug/kdepim-4.99.40/templateparser/templateparser.cpp:273 #9 0x00007f30f3986dff in MessageComposer::MessageFactory::createReply() (this=this@entry=0x7fffe1c05620) at /usr/src/debug/kdepim-4.99.40/messagecomposer/helper/messagefactory.cpp:326 #10 0x00007f30f4a8e4ea in KMReplyCommand::execute() (this=0x5ed21b0) at /usr/src/debug/kdepim-4.99.40/kmail/kmcommands.cpp:845 #11 0x00007f30f4a86ff1 in KMCommand::slotPostTransfer(KMCommand::Result) (this=0x5ed21b0, result=KMCommand::OK) at /usr/src/debug/kdepim-4.99.40/kmail/kmcommands.cpp:261 #12 0x00007f318562313f in QMetaObject::activate(QObject*, int, int, void**) (a=0x7fffe1c05840, r=0x5ed21b0, this=0x49fa8e0) at ../../src/corelib/kernel/qobject_impl.h:124 #13 0x00007f318562313f in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x5ed21b0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffe1c05840) at kernel/qobject.cpp:3702 #14 0x00007f3185623ce7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5ed21b0, m=m@entry=0x7f30f4e4f940 <KMCommand::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffe1c05840) at kernel/qobject.cpp:3582 #15 0x00007f30f4ba398e in KMCommand::messagesTransfered(KMCommand::Result) (this=this@entry=0x5ed21b0, _t1=_t1@entry=KMCommand::OK) at /usr/src/debug/kdepim-4.99.40/build/kmail/moc_kmcommands.cpp:185 #16 0x00007f30f4a89b63 in KMCommand::slotJobFinished() (this=0x5ed21b0) at /usr/src/debug/kdepim-4.99.40/kmail/kmcommands.cpp:370 #17 0x00007f318562313f in QMetaObject::activate(QObject*, int, int, void**) (a=0x7fffe1c059f0, r=0x5ed21b0, this=0x389ad60) at ../../src/corelib/kernel/qobject_impl.h:124 #18 0x00007f318562313f in QMetaObject::activate(QObject*, int, int, void**) (sender=0x3f4b190, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffe1c059f0) at kernel/qobject.cpp:3702 #19 0x00007f31809fbff2 in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5 #20 0x00007f31809fc82c in KJob::emitResult() () at /usr/lib64/libKF5CoreAddons.so.5 #21 0x00007f317ff253a9 in () at /usr/lib64/libKF5AkonadiCore.so.5 #22 0x00007f31856244c6 in QObject::event(QEvent*) (this=0x3f4b190, e=<optimized out>) at kernel/qobject.cpp:1245 #23 0x00007f318674fb5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x1ff86d0, receiver=receiver@entry=0x3f4b190, e=e@entry=0x49fb340) at kernel/qapplication.cpp:3722 #24 0x00007f3186754bc0 in QApplication::notify(QObject*, QEvent*) (this=0x7fffe1c06400, receiver=0x3f4b190, e=0x49fb340) at kernel/qapplication.cpp:3505 #25 0x00007f31855f3e45 in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7fffe1c06400, receiver=0x3f4b190, event=event@entry=0x49fb340) at kernel/qcoreapplication.cpp:930 #26 0x00007f31855f5cdf in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (event=0x49fb340, receiver=<optimized out>) at kernel/qcoreapplication.h:228 #27 0x00007f31855f5cdf in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1fdaaa0) at kernel/qcoreapplication.cpp:1534 #28 0x00007f31855f6318 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1392 #29 0x00007f318564bd13 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x2056c00) at kernel/qeventdispatcher_glib.cpp:271 #30 0x00007f317bae4cb4 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #31 0x00007f317bae4f08 in () at /usr/lib64/libglib-2.0.so.0 #32 0x00007f317bae4fac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #33 0x00007f318564b18c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x204a640, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #34 0x00007f31855f1d9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7fffe1c06040, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #35 0x00007f31855f9426 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1183 #36 0x00000000004041eb in main () What is your template ? (In reply to Laurent Montel from comment #4) > What is your template ? the default? I did not change anything in that regard. I got the same problem. Tried to remove %ODATE and %OTIMELONG from the default reply template and the problem is gone. Surely it's not a fix This bug has never been confirmed for a Kontact version that is based on KDE Frameworks (5.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 oportunity 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. |