kontact-20140713-140728.kcrash Application: kontact (4.13.2) KDE Platform Version: 4.13.2 Qt Version: 4.8.6 Operating System: Linux 3.13.0-24-generic x86_64 Distribution: Linux Mint 17 Qiana -- Information about the crash: - What I was doing when the application crashed: Created a new App't / Event on today's date, in Month View. Saved it & it looked ok. Changed to Week View & was perplexed to see that my new Event was NOT visible in this view. Changed back to Month View ... it was still there. Changed back to Week View ... it was still NOT there. Annoyed, i assumed the app was confused so i Closed Kontact; it responded with an apparently normal SD. However upon my attempted restart of Kontact, this Bug Dialog appeared, thus i knew that indeed something HAD gone wrong & it was not just my imagination. - Unusual behavior I noticed: As above. I am using Mint 17 Qiana KDE. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0ad4eb3800 (LWP 16838))] Thread 7 (Thread 0x7f0ab372b700 (LWP 16839)): #0 0x00007f0acc37a414 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007f0acfc5481d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f0acfc54859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f0acc376182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x00007f0ad242830d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f0a72e28700 (LWP 16840)): #0 0x00007f0acc37a414 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007f0acf99520d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f0acfc83fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f0acc376182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x00007f0ad242830d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f0a638c0700 (LWP 16846)): #0 0x00007f0ad241afbd in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f0acbe96fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f0acbe970ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f0ad2ba17be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007f0ad2b730af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007f0ad2b733a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007f0ad2a6fc5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007f0ad2a7232f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007f0acc376182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x00007f0ad242830d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f0a5bfff700 (LWP 16854)): #0 0x00007f0acbed862a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007f0acbed89b9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f0acbe96680 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f0acbe96f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f0acbe970ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f0ad2ba17be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007f0ad2b730af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007f0ad2b733a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007f0ad2a6fc5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007f0ad2b54823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x00007f0ad2a7232f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x00007f0acc376182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #12 0x00007f0ad242830d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f0a58a4c700 (LWP 17323)): #0 0x00007f0acc37a414 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007f0a69d65ffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x00007f0a69d66039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x00007f0acc376182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x00007f0ad242830d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f09d212d700 (LWP 17413)): #0 0x00007f0ad241afbd in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f0acbe96fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f0acbe970ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f0ad2ba17be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007f0ad2b730af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007f0ad2b733a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007f0ad2a6fc5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007f0ad2b54823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007f0ad2a7232f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007f0acc376182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x00007f0ad242830d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f0ad4eb3800 (LWP 16838)): [KCrash Handler] #5 0x00007f0ad2363f79 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x00007f0ad2367388 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x00007f0ad2a67c92 in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007f0ad2a67ff9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007f0ad2a68804 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x00007f0a68c419d7 in MailCommon::Kernel::self() () from /usr/lib/libmailcommon.so.4 #11 0x00007f0a68c88680 in MailCommon::FolderCollection::writeConfig() const () from /usr/lib/libmailcommon.so.4 #12 0x00007f0a68c88ef2 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib/libmailcommon.so.4 #13 0x00007f0a68c88f69 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib/libmailcommon.so.4 #14 0x00007f0a68c877a4 in ?? () from /usr/lib/libmailcommon.so.4 #15 0x00007f0ad2369509 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #16 0x00007f0ad2369555 in exit () from /lib/x86_64-linux-gnu/libc.so.6 #17 0x00007f0ad300e3de in KCmdLineArgs::isSet(QByteArray const&) const () from /usr/lib/libkdecore.so.5 #18 0x0000000000403f17 in _start () Possible duplicates by query: bug 337087, bug 335457, bug 335011, bug 332229, bug 330850. Report to https://bugs.kde.org/ Reproducible: Didn't try
UPDATE: Upon restarting Kontact after posting this Bug report, i was upset to note the following additional observations in Calendar / KOrganizer: 1. All my customised icons [selection & arrangement] in the toolbar were lost; it was back to default. 2. All my carefully thought-out colourised Categories were lost, & default values had returned. 3. To add insult to injury, my new App't is STILL MISSING in Week View, but STILL VISIBLE in Month View. I am Not Happy ... i was in the process of migrating away from Windows to avoid these kind of disappointments...
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.