Bug 245324 - kontact crashed while kmail open or akregator open or minimized on system tray
Summary: kontact crashed while kmail open or akregator open or minimized on system tray
Status: RESOLVED DUPLICATE of bug 208326
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.3
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-21 15:56 UTC by Ruben Salvador
Modified: 2010-08-06 20:48 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 Ruben Salvador 2010-07-21 15:56:03 UTC
Application: kontact (4.4.3)
KDE Platform Version: 4.4.4 (KDE 4.4.4)
Qt Version: 4.6.3
Operating System: Linux 2.6.32-5-amd64 x86_64
Distribution: Debian GNU/Linux testing (squeeze)

-- Information about the crash:
From today (July 21st) kontact began crashing for no apparent reason. As the title says, it has crashed while minimized on tray, while using akregator, while using kmail, after sending email...

I reopen it and crashes again after a while. Same happen if system is restarted.

No idea how to offer a clearer explanation....

The crash can be reproduced every time.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently asm".
[KCrash Handler]
#5  0x00007f48ade8aa9e in KMail::SearchJob::slotSearchDataSingleMessage (this=0x35f9d80, job=<value optimized out>, data=...) at ../../kmail/searchjob.cpp:424
#6  0x00007f48ade8e442 in KMail::SearchJob::qt_metacall (this=0x35f9d80, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff719db5f0) at ./searchjob.moc:95
#7  0x00007f48c775b346 in QMetaObject::activate (sender=0x35fa020, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x3001) at kernel/qobject.cpp:3295
#8  0x00007f48c7b6175c in KJob::infoMessage (this=0x19a25e0, _t1=0x35fa020, _t2=<value optimized out>, _t3=<value optimized out>) at ./kjob.moc:208
#9  0x00007f48c4ea8337 in KIO::SimpleJobPrivate::_k_slotSlaveInfoMessage (this=<value optimized out>, msg=...) at ../../kio/kio/job.cpp:539
#10 0x00007f48c4eabf4a in KIO::SimpleJob::qt_metacall (this=0x35fa020, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff719db750) at ./jobclasses.moc:178
#11 0x00007f48c775b346 in QMetaObject::activate (sender=0x1bf08b0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x3001) at kernel/qobject.cpp:3295
#12 0x00007f48c4f6c385 in KIO::SlaveInterface::infoMessage (this=0x19a25e0, _t1=<value optimized out>) at ./slaveinterface.moc:287
#13 0x00007f48c4f6f0fe in KIO::SlaveInterface::dispatch (this=0x1bf08b0, _cmd=26, rawdata=...) at ../../kio/kio/slaveinterface.cpp:294
#14 0x00007f48c4f6ca53 in KIO::SlaveInterface::dispatch (this=0x1bf08b0) at ../../kio/kio/slaveinterface.cpp:91
#15 0x00007f48c4f60ec6 in KIO::Slave::gotInput (this=0x1bf08b0) at ../../kio/kio/slave.cpp:324
#16 0x00007f48c4f610ac in KIO::Slave::qt_metacall (this=0x1bf08b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff719dbb40) at ./slave.moc:82
#17 0x00007f48c775b346 in QMetaObject::activate (sender=0x1c00130, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x3001) at kernel/qobject.cpp:3295
#18 0x00007f48c4e7cb07 in KIO::ConnectionPrivate::dequeue (this=0x1bf0880) at ../../kio/kio/connection.cpp:82
#19 0x00007f48c4e7cc2d in KIO::Connection::qt_metacall (this=0x1c00130, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x2afbe80) at ./connection.moc:79
#20 0x00007f48c7757e89 in QObject::event (this=0x1c00130, e=0x23211b0) at kernel/qobject.cpp:1248
#21 0x00007f48c6ae832c in QApplicationPrivate::notify_helper (this=0x11bb560, receiver=0x1c00130, e=0x23211b0) at kernel/qapplication.cpp:4302
#22 0x00007f48c6aee80b in QApplication::notify (this=0x7fff719dc650, receiver=0x1c00130, e=0x23211b0) at kernel/qapplication.cpp:4185
#23 0x00007f48c8130436 in KApplication::notify (this=0x7fff719dc650, receiver=0x1c00130, event=0x23211b0) at ../../kdeui/kernel/kapplication.cpp:302
#24 0x00007f48c774815c in QCoreApplication::notifyInternal (this=0x7fff719dc650, receiver=0x1c00130, event=0x23211b0) at kernel/qcoreapplication.cpp:726
#25 0x00007f48c774b804 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x1192ed0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x1192ed0) at kernel/qcoreapplication.cpp:1367
#27 0x00007f48c7771bd3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#28 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#29 0x00007f48bf0766c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0x00007f48bf07a538 in ?? () from /lib/libglib-2.0.so.0
#31 0x00007f48bf07a6ec in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0x00007f48c7771713 in QEventDispatcherGlib::processEvents (this=0x1192640, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#33 0x00007f48c6b9814e in QGuiEventDispatcherGlib::processEvents (this=0x19a25e0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#34 0x00007f48c7746a82 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#35 0x00007f48c7746e5c in QEventLoop::exec (this=0x7fff719dc590, flags=) at kernel/qeventloop.cpp:201
#36 0x00007f48c774baeb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#37 0x0000000000403e6e in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:224

This bug may be a duplicate of or related to bug 208326.

Possible duplicates by query: bug 242454, bug 242452, bug 236512, bug 208329, bug 208326.

Reported using DrKonqi
Comment 1 Björn Ruberg 2010-08-06 20:48:11 UTC

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