Bug 256918 - kontact crash on viewing e-mail
Summary: kontact crash on viewing e-mail
Status: RESOLVED UNMAINTAINED
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: 2010-11-14 19:46 UTC by Michael Bierbrauer
Modified: 2018-09-04 18:20 UTC (History)
0 users

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 Michael Bierbrauer 2010-11-14 19:46:57 UTC
Application: kontact (4.4.5)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 3"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.5-desktop i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
kontact crashed when I was viewing an e-mail containig html elements

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x00000001 in ?? ()
#7  0xaf2e151e in ?? () from /usr/lib/libkmailprivate.so.4
#8  0xaf5ca581 in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xaf5cd60d in ?? () from /usr/lib/libkmailprivate.so.4
#10 0xb6d2cefd in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#11 0xb6d3bfe8 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#12 0xb6ece7e5 in KJob::result(KJob*) () from /usr/lib/libkdecore.so.5
#13 0xb6ece838 in KJob::emitResult() () from /usr/lib/libkdecore.so.5
#14 0xb56f9e7c in KIO::SimpleJob::slotFinished (this=0x83db6e8) at /usr/src/debug/kdelibs-4.4.4/kio/kio/job.cpp:517
#15 0xb56fa791 in KIO::TransferJob::slotFinished (this=0x83db6e8) at /usr/src/debug/kdelibs-4.4.4/kio/kio/job.cpp:1097
#16 0xb56e3264 in KIO::TransferJob::qt_metacall (this=0x83db6e8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfdce48c)
    at /usr/src/debug/kdelibs-4.4.4/build/kio/jobclasses.moc:367
#17 0xb6d2cefd in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#18 0xb6d3bfe8 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#19 0xb562ca55 in KIO::SlaveInterface::finished (this=0x84f6ec0) at /usr/src/debug/kdelibs-4.4.4/build/kio/slaveinterface.moc:171
#20 0xb575d4ff in KIO::SlaveInterface::dispatch (this=0x84f6ec0, _cmd=104, rawdata=...) at /usr/src/debug/kdelibs-4.4.4/kio/kio/slaveinterface.cpp:175
#21 0xb56b3e8a in KIO::SlaveInterface::dispatch (this=0x84f6ec0) at /usr/src/debug/kdelibs-4.4.4/kio/kio/slaveinterface.cpp:91
#22 0xb56aee98 in KIO::Slave::gotInput (this=0x84f6ec0) at /usr/src/debug/kdelibs-4.4.4/kio/kio/slave.cpp:324
#23 0xb56b802c in KIO::Slave::qt_metacall (this=0x84f6ec0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfdce77c) at /usr/src/debug/kdelibs-4.4.4/build/kio/slave.moc:82
#24 0xb6d2cefd in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#25 0xb6d3bfe8 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#26 0xb56078e5 in KIO::Connection::readyRead (this=0x85b1e48) at /usr/src/debug/kdelibs-4.4.4/build/kio/connection.moc:92
#27 0xb56b7d9a in KIO::ConnectionPrivate::dequeue (this=0x8563850) at /usr/src/debug/kdelibs-4.4.4/kio/kio/connection.cpp:82
#28 0xb56b7e6f in KIO::Connection::qt_metacall (this=0x85b1e48, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x8a05ff0) at /usr/src/debug/kdelibs-4.4.4/build/kio/connection.moc:79
#29 0xb6d2cefd in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#30 0xb6d36945 in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#31 0xb6d3993f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#32 0xb627bc64 in QApplicationPrivate::notify_helper (this=0x8075bf0, receiver=0x85b1e48, e=0x862e108) at kernel/qapplication.cpp:4302
#33 0xb6283bf7 in QApplication::notify (this=0xbfdcf074, receiver=0x85b1e48, e=0x862e108) at kernel/qapplication.cpp:3706
#34 0xb71c69d1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#35 0xb6d26e0e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#36 0xb6d2a9b4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#37 0xb6d2ab9c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#38 0xb6d5283d in ?? () from /usr/lib/libQtCore.so.4
#39 0xb41c9b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#40 0xb41ca350 in ?? () from /usr/lib/libglib-2.0.so.0
#41 0xb41ca60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#42 0xb6d52d4b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#43 0xb632c19a in QGuiEventDispatcherGlib::processEvents (this=0x8056b50, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#44 0xb6d2611d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#45 0xb6d26319 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#46 0xb6d2ac70 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#47 0xb6279164 in QApplication::exec () at kernel/qapplication.cpp:3581
#48 0x0804b813 in _start ()

Possible duplicates by query: bug 256838, bug 256837, bug 256324, bug 256289, bug 256057.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-02-14 15:52:54 UTC
Unfortunately, the backtrace is not helpful.
If you can reproduce this bug, please install the debug package and paste a better one.
More informations on this page: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Andrew Crouthamel 2018-09-04 18:20:42 UTC
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!