[Bug 300007] New: Kontact crashed after refreshing Kalendar
MadMaxCZ
MadMaxCZ at centrum.cz
Mon May 14 15:55:56 BST 2012
https://bugs.kde.org/show_bug.cgi?id=300007
Bug ID: 300007
Severity: crash
Version: unspecified
Priority: NOR
Assignee: kdepim-bugs at kde.org
Summary: Kontact crashed after refreshing Kalendar
Classification: Unclassified
OS: Linux
Reporter: MadMaxCZ at centrum.cz
Hardware: Compiled Sources
Status: UNCONFIRMED
Component: general
Product: kontact
Application: kontact (4.8.0)
KDE Platform Version: 4.8.1 (4.8.1) (Compiled from sources)
Qt Version: 4.8.1
Operating System: Linux 3.0.17-tuxonice-r1 x86_64
Distribution (Platform): Gentoo Packages
-- Information about the crash:
- What I was doing when the application crashed:
Doubleclick on calendar event. Event was created in Kalendar, then updated in
Exchange, then refreshing the Kalendar source to check, if the sync work well.
Then Kontact crashed.
- Custom settings of the application:
Using Exchange calendar via DavMail 3.9.8-1921, which provides CalDAV source on
localhost.
Gentoo, stable KDE 4.8.1 packages.
-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0x7fb6ab4e3760 (LWP 7041))]
Thread 4 (Thread 0x7fb69420e700 (LWP 7042)):
#0 0x00007fb6a336f43c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1 0x00007fb6a7cdf2a4 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4
#2 0x00007fb6a336accc in start_thread () from /lib64/libpthread.so.0
#3 0x00007fb6a8a1ceed in clone () from /lib64/libc.so.6
Thread 3 (Thread 0x7fb69390d700 (LWP 7043)):
#0 0xffffffffff600137 in ?? ()
#1 0x00007fb69390cb20 in ?? ()
#2 0x00007fffd8bff6e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 2 (Thread 0x7fb64b0dc700 (LWP 13038)):
#0 0x00007fb6a336d2a4 in pthread_mutex_lock () from /lib64/libpthread.so.0
#1 0x00007fb6a25d0425 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2 0x00007fb6a25d11e9 in ?? () from /usr/lib64/libglib-2.0.so.0
#3 0x00007fb6a25d1811 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4 0x00007fb6a9e30856 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/qt4/libQtCore.so.4
#5 0x00007fb6a9e010e2 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/qt4/libQtCore.so.4
#6 0x00007fb6a9e01395 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/qt4/libQtCore.so.4
#7 0x00007fb6a9d00d25 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4
#8 0x00007fb6a9de04b8 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#9 0x00007fb6a9d03337 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007fb6a336accc in start_thread () from /lib64/libpthread.so.0
#11 0x00007fb6a8a1ceed in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7fb6ab4e3760 (LWP 7041)):
[KCrash Handler]
#6 0x00007fb6a8978655 in raise () from /lib64/libc.so.6
#7 0x00007fb6a89798fa in abort () from /lib64/libc.so.6
#8 0x00007fb6a9cf96ac in qt_message_output(QtMsgType, char const*) () from
/usr/lib64/qt4/libQtCore.so.4
#9 0x00007fb6a9cf983d in ?? () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007fb6a9cf99d5 in qFatal(char const*, ...) () from
/usr/lib64/qt4/libQtCore.so.4
#11 0x00007fb64f674c4f in MailCommon::Kernel::self() () from
/usr/lib64/libmailcommon.so.4
#12 0x00007fb64f664ca0 in MailCommon::FolderCollection::writeConfig() const ()
from /usr/lib64/libmailcommon.so.4
#13 0x00007fb64f6655e1 in MailCommon::FolderCollection::~FolderCollection() ()
from /usr/lib64/libmailcommon.so.4
#14 0x00007fb64f665679 in MailCommon::FolderCollection::~FolderCollection() ()
from /usr/lib64/libmailcommon.so.4
#15 0x00007fb64f66379e in ?? () from /usr/lib64/libmailcommon.so.4
#16 0x00007fb6a897af59 in ?? () from /lib64/libc.so.6
#17 0x00007fb6a897afa5 in exit () from /lib64/libc.so.6
#18 0x00007fb6aa2aac2b in KCmdLineArgs::isSet(QByteArray const&) const () from
/usr/lib64/libkdecore.so.5
#19 0x00000000004035ad in _start ()
Possible duplicates by query: bug 296226.
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list