Bug 168881 - kmail crash imap image attachment
Summary: kmail crash imap image attachment
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-11 01:16 UTC by Marc Böttcher
Modified: 2008-08-20 17:33 UTC (History)
1 user (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 Marc Böttcher 2008-08-11 01:16:29 UTC
Version:            (using KDE 4.1.0)
Installed from:    SuSE RPMs
OS:                Linux

Anwendung: Kontact (kontact), Signal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb51fe6d0 (LWP 22366)]
[New Thread 0xb075bb90 (LWP 27838)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb1c1fb87 in KMHandleAttachmentCommand::slotStart ()
   from /usr/lib/libkmailprivate.so.4
#7  0xb1c24a53 in KMHandleAttachmentCommand::qt_metacall ()
   from /usr/lib/libkmailprivate.so.4
#8  0xb6be245a in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0xb6be29d2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb6be95a7 in ?? () from /usr/lib/libQtCore.so.4
#11 0xb6be96cc in ?? () from /usr/lib/libQtCore.so.4
#12 0xb6bded7f in QObject::event () from /usr/lib/libQtCore.so.4
#13 0xb5b5decc in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0xb5b6431e in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb721d66d in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0xb6bd0bc1 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0xb6bf91e1 in ?? () from /usr/lib/libQtCore.so.4
#18 0xb6bf945b in QEventDispatcherUNIX::processEvents ()
   from /usr/lib/libQtCore.so.4
#19 0xb5be80a2 in ?? () from /usr/lib/libQtGui.so.4
#20 0xb6bcf33a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#21 0xb6bcf4fa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#22 0xb6bd16dd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#23 0xb5b5dd47 in QApplication::exec () from /usr/lib/libQtGui.so.4
#24 0x0804c17f in _start ()
#0  0xffffe430 in __kernel_vsyscall ()
Comment 1 Oliver Putz 2008-08-11 11:40:31 UTC
Hi, regrettably your backtrace isn't too verbose. Can you reproduce the crash? If so, how? Could you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and give a more verbose backtrace?
Comment 2 Thomas McGuire 2008-08-20 17:33:12 UTC
No comment describing the bug, no backtrace, and I fixed something related recently, closing as invalid.