Bug 423222

Summary: Akonadi crashes while importing mails into KMail
Product: [Frameworks and Libraries] Akonadi Reporter: Claus Christensen <claus_chr>
Component: serverAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: a.samirh78, ach, tnemeth
Priority: NOR Keywords: drkonqi
Version: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi

Description Claus Christensen 2020-06-19 12:35:15 UTC
Application: akonadiserver (5.14.2 (20.04.2))

Qt Version: 5.14.2
Frameworks Version: 5.71.0
Operating System: Linux 4.15.0-106-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.19

-- Information about the crash:
- What I was doing when the application crashed:

I had connected to a POP3-server and was fetching mails (several thousands mails needs to be imported). After having imported hundreds of mails Akonadi crashed. This happened three times in a row.

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted

[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#5  0x00007f8988f05801 in __GI_abort () at abort.c:79
#6  0x00007f898955a957 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x00007f8989560ae6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x00007f8989560b21 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f89898e4e2b in qTerminate () at global/qglobal.cpp:3333
#10 0x00007f8989909dc3 in QThreadPrivate::start (arg=0x55a279ac1c80) at thread/qthread_unix.cpp:354
#11 0x00007f8987a5c6db in start_thread (arg=0x7f897aaad700) at pthread_create.c:463
#12 0x00007f8988fe688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

#1  0x00007f8985e5e2b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f8985e190b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8985e19570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f8985e196dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f8989b587cb in QEventDispatcherGlib::processEvents (this=0x7f897c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x00007f8989af7d2a in QEventLoop::exec (this=this@entry=0x7f8980bf8d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#7  0x00007f8989908757 in QThread::exec (this=this@entry=0x7f898a49ada0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:536
#8  0x00007f898a222555 in QDBusConnectionManager::run (this=0x7f898a49ada0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179
#9  0x00007f8989909c2c in QThreadPrivate::start (arg=0x7f898a49ada0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:342
#10 0x00007f8987a5c6db in start_thread (arg=0x7f8980bf9700) at pthread_create.c:463
#11 0x00007f8988fe688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

#1  0x00007f8985e195c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f8985e196dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8989b587ac in QEventDispatcherGlib::processEvents (this=0x55a279a7e210, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#4  0x00007f8989af7d2a in QEventLoop::exec (this=this@entry=0x7ffdfbf50370, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x00007f8989b014a0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1383
#6  0x000055a2787cf0ea in main (argc=<optimized out>, argv=<optimized out>) at ./src/server/main.cpp:79

Possible duplicates by query: bug 422775, bug 422433, bug 422374, bug 422017, bug 421576.

Reported using DrKonqi
Comment 1 Christoph Feck 2020-07-05 12:35:07 UTC
So unfortunately, these qTerminate() issues are not yet resolved.

If this is reproducible, could you please run the akonadiserver in a terminal and show its output? The message displayed could help understanding the issue.
Comment 2 tnemeth 2020-07-13 09:28:04 UTC
Created attachment 130079 [details]
New crash information added by DrKonqi

akonadiserver (5.13.3 (19.12.3)) using Qt 5.12.8

- What I was doing when the application crashed:
  I was fetching pop3 mails from kmail

- Unusual behavior I noticed:
  Kmail message area went black with a message "PIM service is not operational" with a "Details" button that does nothing.

  I tried renaming ~/.local/share/akonadi to something else and see a a fresh configuration of akonadi could make things work but it failed.

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007f788801c859 in __GI_abort () at abort.c:79
[...]
#11 0x00007f7888469e8b in qTerminate() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#13 0x00007f788784f609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#14 0x00007f7888119103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Comment 3 Achim Bohnet 2020-07-17 17:17:58 UTC
Created attachment 130203 [details]
New crash information added by DrKonqi

akonadiserver (5.14.3 (20.04.3)) using Qt 5.14.2

- What I was doing when the application crashed:

I've selected with Shift-<left> or <right> messages while I was reading/scanning then.  After I pressed 'Del' to move the selected msg to trash akonadi crash after 1 - 2 sec.

-- Backtrace (Reduced):
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#5  0x00007fa7884128b1 in __GI_abort () at abort.c:79
[...]
#9  0x00007fa788df1e2b in qTerminate () at global/qglobal.cpp:3333
#10 0x00007fa788e16dc3 in QThreadPrivate::start (arg=0x562e3eadf610) at thread/qthread_unix.cpp:354
#11 0x00007fa786f686db in start_thread (arg=0x7fa77e2c8700) at pthread_create.c:463
Comment 4 Ahmad Samir 2020-08-18 09:24:06 UTC
Per https://bugs.kde.org/show_bug.cgi?id=401692#c23:
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).
Comment 5 Justin Zobel 2022-10-12 03:50:10 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-10-27 05:03:59 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
mark the bug 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 7 Bug Janitor Service 2022-11-11 05:20:40 UTC
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!