| Summary: | KMail crash when trying load email | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | slav <infoslaw> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | Milos.Kozina+bugs.kde.org, silvan.calarco |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.20.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
slav
2022-07-17 20:48:31 UTC
Created attachment 150932 [details]
New crash information added by DrKonqi
kmail (5.20.3 (22.04.3)) using Qt 5.15.5
- What I was doing when the application crashed:
I just started KMail (or Kontact). Main window was displayed, one last email with attachment was focused, then immediately followed crash o application. No way, how to bypass this. Akonadi seems to work in backround (notifications about new mails are coming).
-- Backtrace (Reduced):
#7 0x00007fa7d6f51833 in __gnu_cxx::__verbose_terminate_handler() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#8 0x00007fa7d6f5dbfc in __cxxabiv1::__terminate(void (*)()) (handler=<optimized out>) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
#9 0x00007fa7d6f5cbba in __cxa_call_terminate(_Unwind_Exception*) (ue_header=0x5575b4a0a480) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_call.cc:54
#10 0x00007fa7d6f5d33a in __cxxabiv1::__gxx_personality_v0(int, _Unwind_Action, _Unwind_Exception_Class, _Unwind_Exception*, _Unwind_Context*) (version=<optimized out>, actions=6, exception_class=5138137972254386944, ue_header=<optimized out>, context=0x7ffcce8e9260) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_personality.cc:688
#11 0x00007fa7d6eac774 in _Unwind_RaiseException_Phase2 (exc=0x5575b4a0a480, context=0x7ffcce8e9260, frames_p=0x7ffcce8e9350) at /usr/src/debug/gcc/libgcc/unwind.inc:64
I have the same problem. In my enviroment I have the suspect that it may be related to libZXing update to 1.4.0. For me this was fixed applying this patch to kitinerary: https://invent.kde.org/pim/kitinerary/-/commit/e60195421aa159462353892ed32bf46ac8c57d19 For me it was corrected by new update of Manjaro packages... Does not happen anymore. |