Bug 228342 - kmail crashed suddenly and inexplicable when i worked with an another app
Summary: kmail crashed suddenly and inexplicable when i worked with an another app
Status: RESOLVED DUPLICATE of bug 191589
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-24 18:03 UTC by salea
Modified: 2010-02-24 22:34 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 salea 2010-02-24 18:03:52 UTC
Application that crashed: kmail
Version of the application: 1.12.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-19-generic i686
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0xb78d4aa0 (LWP 1810))]

Thread 2 (Thread 0xb1ba9b70 (LWP 2603)):
#0  0x004ed422 in __kernel_vsyscall ()
#1  0x02549142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x01b798d4 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0x02a19def in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4  0x02a0e9ae in ?? () from /usr/lib/libQtCore.so.4
#5  0x02a18e32 in ?? () from /usr/lib/libQtCore.so.4
#6  0x0254480e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0x01b6c8de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb78d4aa0 (LWP 1810)):
[KCrash Handler]
#6  0x04321f4d in KIO::Slave::deref() () from /usr/lib/libkio.so.5
#7  0x04322af6 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5
#8  0x04324ee3 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#9  0x02b1f263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#10 0x02b1fec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#11 0x0422cf97 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5
#12 0x0422ed5e in ?? () from /usr/lib/libkio.so.5
#13 0x0422ee8e in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#14 0x02b17f0b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#15 0x02b195fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x0763bf54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0x0764367c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x002e2bfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0x02b096cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#20 0x02b0a2b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#21 0x02b0a47d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#22 0x02b343ff in ?? () from /usr/lib/libQtCore.so.4
#23 0x038a8e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x038ac730 in ?? () from /lib/libglib-2.0.so.0
#25 0x038ac863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x02b3402c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0x076dcbe5 in ?? () from /usr/lib/libQtGui.so.4
#28 0x02b07c79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x02b080ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x02b0a53f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#31 0x0763bdd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#32 0x0804a702 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-24 22:34:23 UTC
Fixed in KDE SC 4.4
Regards

*** This bug has been marked as a duplicate of bug 191589 ***