Summary: | KMail crashed when opening a mailbox folder | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Dennis Schridde <heri+kde> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | heri+kde |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.12.3 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=414436 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Dennis Schridde
2019-11-22 23:43:05 UTC
Reproducible: every time Created attachment 124104 [details]
New crash information added by DrKonqi
kmail (5.12.3) using Qt 5.13.2
- What I was doing when the application crashed:
The crash appears to occur regularly with any email that has appointment information or even invitations attached / contained within.
-- Backtrace (Reduced):
#8 0x00007f2cb820c173 in __gnu_cxx::__verbose_terminate_handler() () at /var/tmp/portage/sys-devel/gcc-9.2.0-r2/work/gcc-9.2.0/libstdc++-v3/libsupc++/vterminate.cc:95
#9 0x00007f2cb823c526 in __cxxabiv1::__terminate(void (*)()) (handler=<optimized out>) at /var/tmp/portage/sys-devel/gcc-9.2.0-r2/work/gcc-9.2.0/libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x00007f2cb823c571 in std::terminate() () at /var/tmp/portage/sys-devel/gcc-9.2.0-r2/work/gcc-9.2.0/libstdc++-v3/libsupc++/eh_terminate.cc:57
#11 0x00007f2cb823c7d4 in __cxxabiv1::__cxa_throw(void*, std::type_info*, void (*)(void*)) (obj=obj@entry=0x55c02dc1fa90, tinfo=0x7f2cb83db0a0 <typeinfo for std::out_of_range>, dest=0x7f2cb8252d70 <std::out_of_range::~out_of_range()>) at /var/tmp/portage/sys-devel/gcc-9.2.0-r2/work/gcc-9.2.0/libstdc++-v3/libsupc++/eh_throw.cc:95
#12 0x00007f2cb820edf8 in std::__throw_out_of_range_fmt(char const*, ...) (__fmt=<optimized out>) at /var/tmp/portage/sys-devel/gcc-9.2.0-r2/work/gcc-9.2.0/libstdc++-v3/src/c++11/functexcept.cc:82
*** This bug has been marked as a duplicate of bug 412251 *** |