| Summary: | KMail repeatedly crashed when i wanted to open attached RAR file with Ark | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | martin knocik <martinknocik> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 4.4.5 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
martin knocik
2010-08-31 11:23:44 UTC
(In reply to comment #0) > Application: kontact (4.4.5) > KDE Platform Version: 4.5.00 (KDE 4.5.0) > Qt Version: 4.6.3 > Operating System: Linux 2.6.31.12-0.2-desktop x86_64 > Distribution: "openSUSE 11.2 (x86_64)" > > -- Information about the crash: > - What I was doing when the application crashed: I wanted to open attached RAR > file. I choose open with Ark, and then Kmail crashed. > > -- Backtrace: > Application: Kontact (kontact), signal: Segmentation fault > [KCrash Handler] > #6 deref (this=<value optimized out>) at > ../../src/corelib/arch/qatomic_x86_64.h:133 > #7 QByteArray::operator= (this=<value optimized out>) at > tools/qbytearray.cpp:865 > #8 0x00007f1b16a71daa in ?? () from /usr/lib64/libkmailprivate.so.4 > #9 0x00007f1b1696e9b9 in GpgME::Signature::summary() const () from > /usr/lib64/libkmailprivate.so.4 > #10 0x00007f1b16bf59b8 in KMHandleAttachmentCommand::slotStart() () from > /usr/lib64/libkmailprivate.so.4 > #11 0x00007f1b16bf7d96 in > KMHandleAttachmentCommand::qt_metacall(QMetaObject::Call, int, void**) () from > /usr/lib64/libkmailprivate.so.4 > #12 0x00007f1b30f96dd6 in QMetaObject::activate (sender=0x1534840, m=<value > optimized out>, local_signal_index=<value optimized out>, > argv=0xffffffffffd4adc4) at kernel/qobject.cpp:3295 > #13 0x00007f1b30f9e24f in QSingleShotTimer::timerEvent (this=0x1534840) at > kernel/qtimer.cpp:308 > #14 0x00007f1b30f93663 in QObject::event (this=0x1534840, e=0x7fff1be6f700) at > kernel/qobject.cpp:1212 > #15 0x00007f1b303417fc in QApplicationPrivate::notify_helper (this=0x6442d0, > receiver=0x1534840, e=0x7fff1be6f700) at kernel/qapplication.cpp:4302 > #16 0x00007f1b30347ddb in QApplication::notify (this=0x7fff1be6fb60, > receiver=0x1534840, e=0x7fff1be6f700) at kernel/qapplication.cpp:4185 > #17 0x00007f1b319215c6 in KApplication::notify (this=0x7fff1be6fb60, > receiver=0x1534840, event=0x7fff1be6f700) at > /usr/src/debug/kdelibs-4.5.0/kdeui/kernel/kapplication.cpp:310 > #18 0x00007f1b30f83b1c in QCoreApplication::notifyInternal > (this=0x7fff1be6fb60, receiver=0x1534840, event=0x7fff1be6f700) at > kernel/qcoreapplication.cpp:726 > #19 0x00007f1b30fb09d5 in sendEvent (event=<value optimized out>, > receiver=<value optimized out>) at kernel/qcoreapplication.h:215 > #20 QTimerInfoList::activateTimers (event=<value optimized out>, > receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:618 > #21 0x00007f1b30fad4a4 in timerSourceDispatch (source=<value optimized out>) at > kernel/qeventdispatcher_glib.cpp:184 > #22 0x00007f1b284c8dee in g_main_context_dispatch () from > /usr/lib64/libglib-2.0.so.0 > #23 0x00007f1b284cc7b8 in ?? () from /usr/lib64/libglib-2.0.so.0 > #24 0x00007f1b284cc8e0 in g_main_context_iteration () from > /usr/lib64/libglib-2.0.so.0 > #25 0x00007f1b30fad193 in QEventDispatcherGlib::processEvents (this=0x613230, > flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 > #26 0x00007f1b303f021e in QGuiEventDispatcherGlib::processEvents > (this=0x131c600, flags=<value optimized out>) at > kernel/qguieventdispatcher_glib.cpp:204 > #27 0x00007f1b30f82432 in QEventLoop::processEvents (this=<value optimized > out>, flags=) at kernel/qeventloop.cpp:149 > #28 0x00007f1b30f8280c in QEventLoop::exec (this=0x7fff1be6faa0, flags=) at > kernel/qeventloop.cpp:201 > #29 0x00007f1b30f874bb in QCoreApplication::exec () at > kernel/qcoreapplication.cpp:1003 > #30 0x0000000000403ede in _start () > > Possible duplicates by query: bug 242241, bug 232039. > > Reported using DrKonqi *** This bug has been marked as a duplicate of bug 188142 *** |