Summary: | akonadi crashed while deleting emails | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Ted Parvu <ted> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | a.samirh78, dag, kmg952, rostik.medved, vishnugb |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Ted Parvu
2020-05-24 15:45:19 UTC
Created attachment 129701 [details] New crash information added by DrKonqi akonadiserver (5.14.2 (20.04.2)) using Qt 5.15.0 - What I was doing when the application crashed: There was an email stuck in the local outbox. The crash happened when I quit KMail. - Custom settings of the application: 1) I am using a Google account with the newly activated XOAUTH2 mechanism, and sending mails does not always work properly. Refer to: https://bugs.kde.org/show_bug.cgi?id=421664 2) I am using KMail with XWayland in a Wayland session. -- Backtrace (Reduced): #6 0x00007f21c2cbb86a in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #7 0x00007f21c2cc7d8a in __cxxabiv1::__terminate (handler=<optimized out>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #8 0x00007f21c2cc7df7 in std::terminate () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58 #9 0x00007f21c2e91cff in qTerminate() () from /usr/lib/libQt5Core.so.5 [...] #3 0x00007f21c310d22c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 Created attachment 129807 [details]
New crash information added by DrKonqi
akonadiserver (5.14.2 (20.04.2)) using Qt 5.15.0
This also happened to me when I just closed KOrganizer. I didn't make any changes to any of my calendars, just reading.
-- Backtrace (Reduced):
#6 0x00007f8ab41ae86a in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#7 0x00007f8ab41bad8a in __cxxabiv1::__terminate (handler=<optimized out>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
#8 0x00007f8ab41badf7 in std::terminate () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
#9 0x00007f8ab4384cff in qTerminate() () from /usr/lib/libQt5Core.so.5
[...]
#3 0x00007f8ab45fe3ba in QTimerInfoList::updateCurrentTime() () from /usr/lib/libQt5Core.so.5
This is a "me too" comment. The crash happens nearly every time I delete multiple (say 8) emails. Very annoying. The backtraces aren't very useful, but the error logs are much more informative in such cases (see ~/.xsession-errors or ~/.local/share/sddm/xorg-session.log for sddm users). (FTR, not marking as duplicate of bug 401692 yet). Created attachment 134530 [details]
New crash information added by DrKonqi
akonadiserver (5.13.2 (19.12.2)) using Qt 5.14.2
- What I was doing when the application crashed:
Deleting about 2000 email from my inbox
It is as simple as that. The same thing happened when moving about 4000 emails from INBOX to Archive/2019 folder. I am also using IMAPS.
-- Backtrace (Reduced):
#9 0x00007fc3f7595e25 in qTerminate() () from /lib64/libQt5Core.so.5
[...]
|