|Summary:||KMail crashes wheh searching inbox.|
|Product:||[Applications] kontact||Reporter:||Andrew Christianson <andrew.christianson>|
|Component:||general||Assignee:||kdepim bugs <kdepim-bugs>|
|Latest Commit:||Version Fixed In:|
Description Andrew Christianson 2015-09-07 22:56:50 UTC
Comment 1 Denis Kurz 2017-06-23 20:22:56 UTC
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.
Comment 2 Wolfgang Schindler 2018-01-29 09:38:37 UTC
Same here with kmail2 5.7.1 / kontact 5.7.1 <code> terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid Received signal 6 #0 0x7f33ceb5fcb7 <unknown> #1 0x7f33cd90c49e <unknown> #2 0x7f33ceb6004d <unknown> #3 0x7f33dd4db940 <unknown> #4 0x7f33dd4db8c7 __GI_raise #5 0x7f33dd4dcc9a __GI_abort #6 0x7f33ddaf82e5 __gnu_cxx::__verbose_terminate_handler() #7 0x7f33ddaf60d6 <unknown> #8 0x7f33ddaf6121 std::terminate() #9 0x7f33ddaf6363 __cxa_throw #10 0x7f33ddb1eb6f std::__throw_logic_error() #11 0x7f33ddb38c69 std::string::_S_construct<>() #12 0x7f33ddb3900c std::string::string() #13 0x7f333e493e31 <unknown> #14 0x7f333cc97586 <unknown> #15 0x7f333cce366f <unknown> #16 0x7f33de087a83 QMetaObject::activate() #17 0x7f33de094ad7 QTimer::timeout() #18 0x7f33de094db2 QTimer::timerEvent() #19 0x7f33de088af4 QObject::event() #20 0x7f33ded6a71c QApplicationPrivate::notify_helper() #21 0x7f33ded71500 QApplication::notify() #22 0x7f33de05d115 QCoreApplication::notifyInternal2() #23 0x7f33de0af41e QTimerInfoList::activateTimers() #24 0x7f33de0afa61 <unknown> #25 0x7f33d740d134 g_main_context_dispatch #26 0x7f33d740d388 <unknown> #27 0x7f33d740d42c g_main_context_iteration #28 0x7f33de0afd8c QEventDispatcherGlib::processEvents() #29 0x7f33badc4c91 <unknown> #30 0x7f33de05b83b QEventLoop::exec() #31 0x7f33de063ef4 QCoreApplication::exec() #32 0x000000404718 <unknown> #33 0x7f33dd4c76d5 __libc_start_main #34 0x000000404c99 _start r8: 000000000000000a r9: 00007f33e0b22780 r10: 0000000000000008 r11: 0000000000000202 r12: 00000000073c3c90 r13: 00007fff7ff6e810 r14: 00007fff7ff6e7f0 r15: 00007fff7ff6e830 di: 000000000000173b si: 000000000000173b bp: 00007f33dd8436d8 bx: 0000000008499f38 dx: 0000000000000006 ax: 0000000000000000 cx: 00007f33dd4db8c7 sp: 00007fff7ff6df98 ip: 00007f33dd4db8c7 efl: 0000000000000202 cgf: 0000000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated. </code>
Comment 3 Wolfgang Schindler 2018-01-29 10:00:29 UTC
Forgot: Opensuse 42.3
Comment 4 Andrew Crouthamel 2018-09-28 03:24:46 UTC
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-29 02:19:58 UTC
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!