Bug 184240 - The application Kontact (kontact) crashed and caused the signal 6 (SIGABRT). when clicking 'reply' to message.
Summary: The application Kontact (kontact) crashed and caused the signal 6 (SIGABRT). ...
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-13 19:29 UTC by chris olive
Modified: 2009-03-19 00:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description chris olive 2009-02-13 19:29:42 UTC 
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).>
Comment 1 Jaime Torres 2009-02-13 20:29:57 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 :)
Comment 2 chris olive 2009-02-14 12:17:41 UTC 
(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
Comment 3 Jaime Torres 2009-02-14 12:32:08 UTC 
Not yet, sorry.
The interesting parts are in #35 and bellow.
Comment 4 chris olive 2009-02-18 10:20:38 UTC 
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