Bug 352801 - Kontact crashes when starting new instance
Summary: Kontact crashes when starting new instance
Status: RESOLVED DUPLICATE of bug 351686
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-09-16 15:01 UTC by Robert G. Siebeck
Modified: 2015-09-26 14:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert G. Siebeck 2015-09-16 15:01:32 UTC
Application: kontact (4.14.10)
KDE Platform Version: 4.14.11 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 4.0.5-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

Started Kontact. Kontact then crashed. Starting the next time works without any problems.

This problem occurs regularily, but not every time I start Kontact.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9fe6ddc780 (LWP 2130))]

Thread 3 (Thread 0x7f9fd0462700 (LWP 2131)):
#0  0x00007f9fdec3154f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f9fe255268a in ?? () from /usr/lib64/qt4/libQtWebKit.so.4
#2  0x00007f9fe25526c9 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4
#3  0x00007f9fdec2d204 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f9fe438846d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f9fcfb61700 (LWP 2132)):
#0  0x00007f9fe437f87d in poll () from /lib64/libc.so.6
#1  0x00007f9fdde04b74 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f9fdde04c8c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f9fe576963e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007f9fe573b59f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#5  0x00007f9fe573b895 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#6  0x00007f9fe5639cdf in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4
#7  0x00007f9fe563c3bf in ?? () from /usr/lib64/qt4/libQtCore.so.4
#8  0x00007f9fdec2d204 in start_thread () from /lib64/libpthread.so.0
#9  0x00007f9fe438846d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f9fe6ddc780 (LWP 2130)):
[KCrash Handler]
#5  0x00007f9fe42d5e77 in raise () from /lib64/libc.so.6
#6  0x00007f9fe42d71da in abort () from /lib64/libc.so.6
#7  0x00007f9fe5631ee4 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/qt4/libQtCore.so.4
#8  0x00007f9fe5632069 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007f9fe5632874 in qFatal(char const*, ...) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007f9fcc07d1b7 in MailCommon::Kernel::self() () from /usr/lib64/libmailcommon.so.4
#11 0x00007f9fcc0c5400 in MailCommon::FolderCollection::writeConfig() const () from /usr/lib64/libmailcommon.so.4
#12 0x00007f9fcc0c5c02 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib64/libmailcommon.so.4
#13 0x00007f9fcc0c5c79 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib64/libmailcommon.so.4
#14 0x00007f9fcc0c4534 in ?? () from /usr/lib64/libmailcommon.so.4
#15 0x00007f9fe42d8679 in ?? () from /lib64/libc.so.6
#16 0x00007f9fe42d86c5 in exit () from /lib64/libc.so.6
#17 0x00007f9fe5be293e in KCmdLineArgs::isSet(QByteArray const&) const () from /usr/lib64/libkdecore.so.5
#18 0x0000000000403e67 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 341852.

Possible duplicates by query: bug 351686, bug 351213, bug 351178, bug 350841, bug 350570.

Reported using DrKonqi
Comment 1 Allen Winter 2015-09-26 14:36:17 UTC

*** This bug has been marked as a duplicate of bug 351686 ***