Hello, I recently did a fresh install of my Xubuntu (Xubuntu/Ubuntu 14.04.2 LTS trusty) system. I copied these old folders form my old system to the new one: ~/.kde/share/apps/kmail2/* ~/.kde/share/config/akonadi* ~/.kde/share/config/kmail* ~/.kde/share/config/emaildefaults ~/.kde/share/config/emailidentities ~/.kde/share/config/mailtransports ~/.kde/share/apps/emailidentities/* ~/.local/share/local-mail/* ~/.local/share/akonadi/* ~/.config/akonadi/* ~/.kde/share/apps/nepomuk/* ~/.kde/share/config/nepomukserverrc At first, Kmail seemed to work fine, although the search messages functionality was not fully available. But now, I get this error message on starting up Kmail: The Email program encountered a fatal error and will terminate now. The error was: Unable to append mimetype for collection drafts resourceId: 3 The strange thing is that some things seem to work as normal (still able to receive messages and create new mail, but not able to view message), until I click to "ok" button of kmail, which causes it to terminate immediately. I don't know if this is related, but I also seem to have two "Local Folders" trees. Thanks in advance for your help. Reproducible: Always Steps to Reproduce: 1. start kmail 2. 3.
When kmail is terminated after the error message is shown, it sometimes gives the following bug report: Executable: kmail PID: 3440 Signal: Aborted (6) Time: 04/26/15 09:42:46 PM Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f08ac7bc800 (LWP 3440))] Thread 5 (Thread 0x7f08809cf700 (LWP 3443)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f089e0b481d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f089e0b4859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f08a73da182 in start_thread (arg=0x7f08809cf700) at pthread_create.c:312 #4 0x00007f08a9b1847d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f082d490700 (LWP 3444)): #0 0x00007f08a1bd8627 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007f08a1bd89a9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f08a1b96718 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f08a1b96f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f08a1b9730a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f088a1cb336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x00007f08a1bbbf05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x00007f08a73da182 in start_thread (arg=0x7f082d490700) at pthread_create.c:312 #8 0x00007f08a9b1847d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f0827fff700 (LWP 3445)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f089ddf520d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f089e0e3fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f08a73da182 in start_thread (arg=0x7f0827fff700) at pthread_create.c:312 #4 0x00007f08a9b1847d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f08273fe700 (LWP 3446)): #0 0x00007f08a9b0b12d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f08a1b96fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f08a1b970ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f08aa4a77be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007f08aa4790af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007f08aa4793a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007f08aa375c5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007f08aa37832f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007f08a73da182 in start_thread (arg=0x7f08273fe700) at pthread_create.c:312 #9 0x00007f08a9b1847d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f08ac7bc800 (LWP 3440)): [KCrash Handler] #5 0x00007f08a9a54cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #6 0x00007f08a9a580d8 in __GI_abort () at abort.c:89 #7 0x00007f08aa36dc92 in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007f08aa36dff9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007f08aa36e804 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x00007f08ac29a19f in KMainWindow::memberList() () from /usr/lib/libkdeui.so.5 #11 0x00007f08ab541c8b in KMKernel::dumpDeadLetters() () from /usr/lib/libkmailprivate.so.4 #12 0x00007f08ab543527 in ?? () from /usr/lib/libkmailprivate.so.4 #13 0x00007f08ac244078 in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdeui.so.5 #14 <signal handler called> #15 0x00007f08a9a54cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #16 0x00007f08a9a580d8 in __GI_abort () at abort.c:89 #17 0x00007f08aa36dc92 in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x00007f08aa36dff9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #19 0x00007f08aa36e804 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #20 0x00007f08a52839d7 in MailCommon::Kernel::self() () from /usr/lib/libmailcommon.so.4 #21 0x00007f08a52ca680 in MailCommon::FolderCollection::writeConfig() const () from /usr/lib/libmailcommon.so.4 #22 0x00007f08a52caef2 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib/libmailcommon.so.4 #23 0x00007f08a52caf69 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib/libmailcommon.so.4 #24 0x00007f08a52c97a4 in ?? () from /usr/lib/libmailcommon.so.4 #25 0x00007f08a9a5a5ea in __cxa_finalize (d=0x7f08a55878d8) at cxa_finalize.c:56 #26 0x00007f08a5282393 in ?? () from /usr/lib/libmailcommon.so.4 #27 0x00007fffd255afc0 in ?? () #28 0x00007f08ac61d73a in _dl_fini () at dl-fini.c:252 Backtrace stopped: frame did not save the PC
This is the contents of akonadiserver.error/akonadiserver.error.old: DATABASE ERROR: Error code: 1062 DB error: "Duplicate entry '52-5' for key 'PRIMARY'" Error text: "Duplicate entry '52-5' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Query: "INSERT INTO CollectionMimeTypeRelation (Collection_id, MimeType_id) VALUES (:0, :1)" DATABASE ERROR: Error code: 1062 DB error: "Duplicate entry '53-5' for key 'PRIMARY'" Error text: "Duplicate entry '53-5' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Query: "INSERT INTO CollectionMimeTypeRelation (Collection_id, MimeType_id) VALUES (:0, :1)" DATABASE ERROR: Error code: 1062 DB error: "Duplicate entry '54-5' for key 'PRIMARY'" Error text: "Duplicate entry '54-5' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Query: "INSERT INTO CollectionMimeTypeRelation (Collection_id, MimeType_id) VALUES (:0, :1)" DATABASE ERROR: Error code: 1062 DB error: "Duplicate entry '55-5' for key 'PRIMARY'" Error text: "Duplicate entry '55-5' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Query: "INSERT INTO CollectionMimeTypeRelation (Collection_id, MimeType_id) VALUES (:0, :1)" Control process died, committing suicide!
Thank you for reporting the bug. Please install the necessary debug packages, at least kdepim-dbg, kdepimlibs-dbg, kde-runtime-dbg, libqt4-dbg but probably also others so that the backtrace ideally does not contain any ??? anymore. Please also start Kmail from command line and paste the output, enable debug output in kdebugdialog before (remember to disable again unless you want a huge ~/.xsession-errors). Thanks, Martin
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 set the bug status 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!
Dear Bug Submitter, 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!