| Summary: | The application Kontact (kontact) crashed and caused the signal 6 (SIGABRT). when clicking 'reply' to message. | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | chris olive <chris.olive> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
chris olive
2009-02-13 19:29:42 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :) (In reply to comment #0) > Version: (using KDE 4.1.3) > OS: Linux > Installed from: Ubuntu Packages > > friends are kept in there own in-box's as sub folders in in-box when clicking > 'reply' in one of these the system crashes giving this message <The application > Kontact (kontact) crashed and caused the signal 6 (SIGABRT).> >Saturday 14th Feb In reply to e-mail from bugsquad-triage@kde.org, there are six sub-folders in my in-box only one causes a crash I have deleted the box and set it up again but the problem is still there this is the bug report below. #36 0xb7ebc520 in ?? () from /usr/lib/libQtCore.so.4 #37 0xb6a6e6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #38 0xb6a71da3 in ?? () from /usr/lib/libglib-2.0.so.0 #39 0xb6a71f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #40 0xb7ebc478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #41 0xb6f32ea5 in ?? () from /usr/lib/libQtGui.so.4 #42 0xb7e9052a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #43 0xb7e906ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #44 0xb7e92da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #45 0xb6e98767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #46 0x0804bf52 in _start () #0 0xb7fa8430 in __kernel_vsyscall () Hope this helps many thanks Chris Not yet, sorry. The interesting parts are in #35 and bellow. Checked this box to day and it works fine now, I still have no idea what caused the problem but am happy now. Many thanks to all at Bugsquad and all who replyed. Chris |