Bug 177585 - KMail crashed when moving a mail to a different folder
Summary: KMail crashed when moving a mail to a different folder
Status: RESOLVED REMIND
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.10.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-12 13:38 UTC by jde3
Modified: 2009-03-19 00:36 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 jde3 2008-12-12 13:38:52 UTC
Version:           1.10.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

I got the following report :

Application : KMail (kmail), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb412f6c0 (LWP 26103)]
[New Thread 0xab37cb90 (LWP 7089)]
[KCrash handler]
#6  0xb77abea1 in ?? () from /usr/lib/libkmailprivate.so.4
#7  0xb7418646 in ?? () from /usr/lib/libkmailprivate.so.4
#8  0xb777f95d in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xb7783ee4 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0xb7e48a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7e497e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb7bad283 in KJob::result (this=0x8e90e78, _t1=0x8e90e78)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kdecore/kjob.moc:186
#13 0xb7bad792 in KJob::emitResult (this=0x8e90e78)
    at /build/buildd/kde4libs-4.1.3/kdecore/jobs/kjob.cpp:290
#14 0xb53478c5 in KIO::SimpleJob::slotFinished (this=0x8e90e78)
    at /build/buildd/kde4libs-4.1.3/kio/kio/job.cpp:498
#15 0xb534e353 in KIO::TransferJob::slotFinished (this=0x8e90e78)
    at /build/buildd/kde4libs-4.1.3/kio/kio/job.cpp:967
#16 0xb534f12b in KIO::TransferJob::qt_metacall (this=0x8e90e78, 
    _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfa4a778)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/jobclasses.moc:336
#17 0xb7e48a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb7e497e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb540df27 in KIO::SlaveInterface::finished (this=0x8e1d898)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/slaveinterface.moc:161
#20 0xb5411b97 in KIO::SlaveInterface::dispatch (this=0x8e1d898, _cmd=104, 
    rawdata=@0xbfa4a944)
    at /build/buildd/kde4libs-4.1.3/kio/kio/slaveinterface.cpp:175
#21 0xb540e6a7 in KIO::SlaveInterface::dispatch (this=0x8e1d898)
    at /build/buildd/kde4libs-4.1.3/kio/kio/slaveinterface.cpp:90
#22 0xb53fe6cd in KIO::Slave::gotInput (this=0x8e1d898)
    at /build/buildd/kde4libs-4.1.3/kio/kio/slave.cpp:322
#23 0xb5401113 in KIO::Slave::qt_metacall (this=0x8e1d898, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfa4aa58)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/slave.moc:75
#24 0xb7e48a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#25 0xb7e497e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#26 0xb530e8f7 in KIO::Connection::readyRead (this=0x8e1e0a8)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/connection.moc:84
#27 0xb53109c9 in KIO::ConnectionPrivate::dequeue (this=0x8e1e0c8)
    at /build/buildd/kde4libs-4.1.3/kio/kio/connection.cpp:82
#28 0xb5310b56 in KIO::Connection::qt_metacall (this=0x8e1e0a8, 
    _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x9a43e78)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/connection.moc:72
#29 0xb7e41bfb in QMetaCallEvent::placeMetaCall ()
   from /usr/lib/libQtCore.so.4
#30 0xb7e43771 in QObject::event () from /usr/lib/libQtCore.so.4
#31 0xb67228ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#32 0xb672a72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#33 0xb70b9b2d in KApplication::notify (this=0xbfa4b2a8, receiver=0x8e1e0a8, 
    event=0x9a024b8)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#34 0xb7e33e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#35 0xb7e34ae5 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#36 0xb7e34cdd in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#37 0xb7e5e82f in ?? () from /usr/lib/libQtCore.so.4
#38 0xb62e86f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#39 0xb62ebda3 in ?? () from /usr/lib/libglib-2.0.so.0
#40 0xb62ebf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#41 0xb7e5e478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#42 0xb67bcea5 in ?? () from /usr/lib/libQtGui.so.4
#43 0xb7e3252a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#44 0xb7e326ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#45 0xb7e34da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#46 0xb6722767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#47 0x0804a6c0 in _start ()
#0  0xb7f4b430 in __kernel_vsyscall ()
Comment 1 George Goldberg 2008-12-12 14:50:28 UTC
Unfortunately the backtrace provided does not contain enough information for us to try and fix the bug. If you are still able to reproduce the bug, please would you take a look at this page which explains how to get a backtrace that is more useful to us. 

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks
Comment 2 Jaime Torres 2009-01-19 11:38:24 UTC
After one month without news, this bug is closed until more information is provided.

If you still experience this bug and are able to provide a backtrace with more information, feel free to reopen the bug.