[Solved] Issue with Kmail after last upgrade

iyanmv · 2019-12-15 11:33:06

After last KDE Apps upgrade (19.12.0), I can't use Kmail. I continuously get a akonadi_imap_resource Segmentation fault error in one of my accounts. Kmail itself does not crash but, as expected, I don't receive any emails, and I can't open the IMAP configuration window of the affected account. What it's a bit strange is that only one account seems to be affected and I can use the rest normally.

I have already tried to stop akonadi, delete Akonadi database and config folders and configure Kmail again but I got same error again. I also couldn't find any bug on the KDE Bugtracking System that fits exactly my issue.

Anyone else experiencing a similar problem after last upgrade?

Edit 1/1/2020

I decided to compile akonadi-mime package with debug options in order to get a useful trace and fill a bug upstream. Problem was solved after installing my package. Later I tried recompiling original PKGBUILD without the debug flags/options and it also works just fine. I guess binary from mirrors doesn't like my computers, I don't understand where this issue could come from. Anyway, problem solved. I will wait till next release of that package, and if official binary still produces the segmentation fault I will report a bug in Archlinux bugtracker.

Last edited by iyanmv (2020-01-01 10:38:51)

ugjka · 2019-12-15 13:48:33

is it Gmail?

iyanmv · 2019-12-15 15:11:20

No, it's an email from my host.

koffeinfriedhof · 2019-12-15 15:19:31

I'm using KMail with 8 different account types (no Gmail atm) and I do not have a segfault.

Could you try adding a new, clean user and set up kmail in his context? Perhaps you got some old configuration stuff or similar which breaks your current kmail. Have a look at `journalctl -b -xep 0..4` too, which shows warnings and errors since last reboot.

iyanmv · 2019-12-15 20:34:24

koffeinfriedhof wrote:

Could you try adding a new, clean user and set up kmail in his context? Perhaps you got some old configuration stuff or similar which breaks your current kmail. Have a look at `journalctl -b -xep 0..4` too, which shows warnings and errors since last reboot.

Still same error with same account.

iyanmv · 2019-12-16 07:46:14

This is the relevant part of the `journalctl -b -xep 0..4` command that was suggested before:

dic 16 08:28:12 theotp40 akonadi_control[2926]: org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" )
dic 16 08:28:12 theotp40 akonadi_control[2926]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed! 1 restarts left.
dic 16 08:28:12 theotp40 systemd-coredump[7548]: Process 2989 (akonadi_imap_re) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 2989:
                                                 #0  0x00007f989cbe9f25 raise (libc.so.6 + 0x3bf25)
                                                 #1  0x00007f98930ddbf0 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5bf0)
                                                 #2  0x00007f989cbe9fb0 __restore_rt (libc.so.6 + 0x3bfb0)
                                                 #3  0x0000559dd6421c00 n/a (akonadi_imap_resource + 0x5ec00)
                                                 #4  0x0000559dd6451487 n/a (akonadi_imap_resource + 0x8e487)
                                                 #5  0x0000559dd64559b5 n/a (akonadi_imap_resource + 0x929b5)
                                                 #6  0x00007f989d242d03 n/a (libQt5Core.so.5 + 0x2c9d03)
                                                 #7  0x00007f989d236495 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2bd495)
                                                 #8  0x00007f989dd804e5 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1594e5)
                                                 #9  0x00007f989dd89e11 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162e11)
                                                 #10 0x00007f989d209d12 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x290d12)
                                                 #11 0x00007f989d260ead _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2e7ead)
                                                 #12 0x00007f989d261742 n/a (libQt5Core.so.5 + 0x2e8742)
                                                 #13 0x00007f989b1d639e g_main_context_dispatch (libglib-2.0.so.0 + 0x6a39e)
                                                 #14 0x00007f989b1d81b1 n/a (libglib-2.0.so.0 + 0x6c1b1)
                                                 #15 0x00007f989b1d81f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
                                                 #16 0x00007f989d261b13 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e8b13)
                                                 #17 0x00007f989d20883c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28f83c)
                                                 #18 0x00007f989d210676 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x297676)
                                                 #19 0x00007f989eca00c2 _ZN7Akonadi12ResourceBase4initERS0_ (libKF5AkonadiAgentBase.so.5 + 0x2e0c2)
                                                 #20 0x0000559dd63ee788 n/a (akonadi_imap_resource + 0x2b788)
                                                 #21 0x00007f989cbd5153 __libc_start_main (libc.so.6 + 0x27153)
                                                 #22 0x0000559dd63ec8ae n/a (akonadi_imap_resource + 0x298ae)
                                                 
                                                 Stack trace of thread 3111:
                                                 #0  0x00007f989cca29ef __poll (libc.so.6 + 0xf49ef)
                                                 #1  0x00007f989b1d8120 n/a (libglib-2.0.so.0 + 0x6c120)
                                                 #2  0x00007f989b1d81f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
                                                 #3  0x00007f989d261b2c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e8b2c)
                                                 #4  0x00007f989d20883c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28f83c)
                                                 #5  0x00007f989d03a305 _ZN7QThread4execEv (libQt5Core.so.5 + 0xc1305)
                                                 #6  0x00007f989d03b530 n/a (libQt5Core.so.5 + 0xc2530)
                                                 #7  0x00007f989c2644cf start_thread (libpthread.so.0 + 0x94cf)
                                                 #8  0x00007f989ccad2d3 __clone (libc.so.6 + 0xff2d3)
                                                 
                                                 Stack trace of thread 3139:
                                                 #0  0x00007f989b1884e4 g_mutex_unlock (libglib-2.0.so.0 + 0x1c4e4)
                                                 #1  0x00007f989b1d8038 n/a (libglib-2.0.so.0 + 0x6c038)
                                                 #2  0x00007f989b1d81f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
                                                 #3  0x00007f989d261b2c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e8b2c)
                                                 #4  0x00007f989d20883c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28f83c)
                                                 #5  0x00007f989d03a305 _ZN7QThread4execEv (libQt5Core.so.5 + 0xc1305)
                                                 #6  0x00007f989d03b530 n/a (libQt5Core.so.5 + 0xc2530)
                                                 #7  0x00007f989c2644cf start_thread (libpthread.so.0 + 0x94cf)
                                                 #8  0x00007f989ccad2d3 __clone (libc.so.6 + 0xff2d3)
                                                 
                                                 Stack trace of thread 3107:
                                                 #0  0x00007f989b1cee38 g_main_context_query (libglib-2.0.so.0 + 0x62e38)
                                                 #1  0x00007f989b1d809d n/a (libglib-2.0.so.0 + 0x6c09d)
                                                 #2  0x00007f989b1d81f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
                                                 #3  0x00007f989d261b2c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e8b2c)
                                                 #4  0x00007f989d20883c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28f83c)
                                                 #5  0x00007f989d03a305 _ZN7QThread4execEv (libQt5Core.so.5 + 0xc1305)
                                                 #6  0x00007f989e323b37 n/a (libQt5DBus.so.5 + 0x15b37)
                                                 #7  0x00007f989d03b530 n/a (libQt5Core.so.5 + 0xc2530)
                                                 #8  0x00007f989c2644cf start_thread (libpthread.so.0 + 0x94cf)
                                                 #9  0x00007f989ccad2d3 __clone (libc.so.6 + 0xff2d3)
                                                 
                                                 Stack trace of thread 3099:
                                                 #0  0x00007f989c26ac45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
                                                 #1  0x00007f988384b60c n/a (i965_dri.so + 0x4e060c)
                                                 #2  0x00007f988384b208 n/a (i965_dri.so + 0x4e0208)
                                                 #3  0x00007f989c2644cf start_thread (libpthread.so.0 + 0x94cf)
                                                 #4  0x00007f989ccad2d3 __clone (libc.so.6 + 0xff2d3)
                                                 
                                                 Stack trace of thread 4753:
                                                 #0  0x00007f989cc9e42c __read (libc.so.6 + 0xf042c)
                                                 #1  0x00007f989b1889f0 n/a (libglib-2.0.so.0 + 0x1c9f0)
                                                 #2  0x00007f989b1d69e1 g_main_context_check (libglib-2.0.so.0 + 0x6a9e1)
                                                 #3  0x00007f989b1d80c8 n/a (libglib-2.0.so.0 + 0x6c0c8)
                                                 #4  0x00007f989b1d81f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
                                                 #5  0x00007f989d261b2c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e8b2c)
                                                 #6  0x00007f989d20883c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28f83c)
                                                 #7  0x00007f989d03a305 _ZN7QThread4execEv (libQt5Core.so.5 + 0xc1305)
                                                 #8  0x00007f989d03b530 n/a (libQt5Core.so.5 + 0xc2530)
                                                 #9  0x00007f989c2644cf start_thread (libpthread.so.0 + 0x94cf)
                                                 #10 0x00007f989ccad2d3 __clone (libc.so.6 + 0xff2d3)
-- Subject: Process 2989 (akonadi_imap_re) dumped core

koffeinfriedhof · 2019-12-16 12:32:56

And this only happens editing one special account? Did you set the mailserver yourself up? Sth. special?

I do not know where to catch this. Try

akonadictl fsck
akonadictl vacuum
akonadictl restart

If you need more tracing of restart output you can use

QT_DEBUG_PLUGINS=1 akonadictl restart

iyanmv · 2019-12-16 16:12:55

koffeinfriedhof wrote:

And this only happens editing one special account? Did you set the mailserver yourself up? Sth. special?

Not really, it's a normal IMAP server provided by Siteground. I didn't set it up myself, and also I cannot modify any configuration files. Basically, I can only create new users and accounts.

koffeinfriedhof wrote:

I do not know where to catch this. Try
akonadictl fsck
akonadictl vacuum
akonadictl restart

I have tried that and for the moment it looks like it's working again. At least I was able to check the emails and there was no crash. I am trying in my laptop, I will try again tomorrow in my desktop and comment here if it also works. By the way, I don't fully understand the output of the previous commands by I copy here some relevant lines:

$ akonadi fsck
...
Found 5 collections without RID.
...
Collection 48 search index contains 1 orphan items. Scheduling reindexing
...
Consistency check done.

$ akonadictl vacuum
...
vacuum done

koffeinfriedhof wrote:

If you need more tracing of restart output you can use
QT_DEBUG_PLUGINS=1 akonadictl restart

Thanks! I will try that if issue persists. Thank you again for helping with this.

koffeinfriedhof · 2019-12-16 18:03:38

akonadis fsck perfoms a check and tries to repair inconsistent data in its local mysql database. The vacuum cleans up older entries, like old content held for restore and similar. I do not know much more about it but in case of uncatchable errors it could help.

Hope you're done with it so far.

iyanmv · 2019-12-17 08:30:16

So there were some crashes in my laptop again (same "/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" )) but despite that, my email was still working. Probably this time, it restarted successfully, no idea. I also execute the same commands in my desktop and it began working again, with no crashes so far. This is hard to debug, I don't even know how to report this bug to KDE bugtracker because I am not able to reproduce. Sometimes it happens, akonadictl fsck + vacuum + restart seems to solve it, but maybe only temporary. I leave the post without "solved" and I update in the future.

iyanmv · 2019-12-17 17:35:46

I found an open bug similar to my issue. I leave here the link just in case someone else has similar problems and wants to add something there.

https://bugs.kde.org/show_bug.cgi?id=414685

iyanmv · 2019-12-26 09:58:28

Today I realized that if I don't lock my desktop, it doesn't happen. But the moment I leave the computer locked, I get the same issue and I have to close Kmail, do the akonadictl fsck + vacuum + restart, and then open Kmail again.

Arch Linux

#1 2019-12-15 11:33:06

[Solved] Issue with Kmail after last upgrade

#2 2019-12-15 13:48:33

Re: [Solved] Issue with Kmail after last upgrade

#3 2019-12-15 15:11:20

Re: [Solved] Issue with Kmail after last upgrade

#4 2019-12-15 15:19:31

Re: [Solved] Issue with Kmail after last upgrade

#5 2019-12-15 20:34:24

Re: [Solved] Issue with Kmail after last upgrade

#6 2019-12-16 07:46:14

Re: [Solved] Issue with Kmail after last upgrade

#7 2019-12-16 12:32:56

Re: [Solved] Issue with Kmail after last upgrade

#8 2019-12-16 16:12:55

Re: [Solved] Issue with Kmail after last upgrade

#9 2019-12-16 18:03:38

Re: [Solved] Issue with Kmail after last upgrade

#10 2019-12-17 08:30:16

Re: [Solved] Issue with Kmail after last upgrade

#11 2019-12-17 17:35:46

Re: [Solved] Issue with Kmail after last upgrade

#12 2019-12-26 09:58:28

Re: [Solved] Issue with Kmail after last upgrade

Board footer