Bug 175563

Summary:	kmail crashes on receiving emails
Product:	[Unmaintained] kmail	Reporter:	edgar klüsener <edgar>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	mail
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description edgar klüsener 2008-11-19 11:17:42 UTC

Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

I have five different email-accounts, four POP3, one IMAP. When checking the accounts for new mail, kmail crashes. This usually happens straight after startup. Krashhandler gives the following information:

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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f4d34858700 (LWP 4296)]
[New Thread 0x40c41950 (LWP 4316)]
(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)
[KCrash handler]
#5  0x00007f4d1d2a8dd0 in ?? () from /usr/lib64/libkmailprivate.so.4
#6  0x00007f4d1d231d04 in ?? () from /usr/lib64/libkmailprivate.so.4
#7  0x00007f4d1d2339ea in ?? () from /usr/lib64/libkmailprivate.so.4
#8  0x00007f4d1d288cab in ?? () from /usr/lib64/libkmailprivate.so.4
#9  0x00007f4d1d28be27 in ?? () from /usr/lib64/libkmailprivate.so.4
#10 0x00007f4d2ef56284 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#11 0x00007f4d1d3c52af in ?? () from /usr/lib64/libkmailprivate.so.4
#12 0x00007f4d1d3d027d in ?? () from /usr/lib64/libkmailprivate.so.4
#13 0x00007f4d1d3d33a7 in ?? () from /usr/lib64/libkmailprivate.so.4
#14 0x00007f4d2ef56284 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#15 0x00007f4d300ad492 in KJob::result () from /usr/lib64/libkdecore.so.5
#16 0x00007f4d300ad807 in KJob::emitResult () from /usr/lib64/libkdecore.so.5
#17 0x00007f4d31131930 in KIO::SimpleJob::slotFinished ()
   from /usr/lib64/libkio.so.5
#18 0x00007f4d311324b3 in KIO::TransferJob::slotFinished ()
   from /usr/lib64/libkio.so.5
#19 0x00007f4d311334f5 in KIO::TransferJob::qt_metacall ()
   from /usr/lib64/libkio.so.5
#20 0x00007f4d2ef56284 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#21 0x00007f4d311d7191 in KIO::SlaveInterface::dispatch ()
   from /usr/lib64/libkio.so.5
#22 0x00007f4d311d50b2 in KIO::SlaveInterface::dispatch ()
   from /usr/lib64/libkio.so.5
#23 0x00007f4d311c88ee in KIO::Slave::gotInput () from /usr/lib64/libkio.so.5
#24 0x00007f4d311c8bf8 in KIO::Slave::qt_metacall ()
   from /usr/lib64/libkio.so.5
#25 0x00007f4d2ef56284 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#26 0x00007f4d311062b1 in ?? () from /usr/lib64/libkio.so.5
#27 0x00007f4d3110695a in KIO::Connection::qt_metacall ()
   from /usr/lib64/libkio.so.5
#28 0x00007f4d2ef50f4d in QObject::event () from /usr/lib64/libQtCore.so.4
#29 0x00007f4d2b36f17d in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#30 0x00007f4d2b376f2a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#31 0x00007f4d30c9cd6b in KApplication::notify () from /usr/lib64/libkdeui.so.5
#32 0x00007f4d2ef41e81 in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#33 0x00007f4d2ef42b3a in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib64/libQtCore.so.4
#34 0x00007f4d2ef6a723 in ?? () from /usr/lib64/libQtCore.so.4
#35 0x00007f4d2822c93a in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#36 0x00007f4d28230040 in ?? () from /usr/lib64/libglib-2.0.so.0
#37 0x00007f4d282301dc in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#38 0x00007f4d2ef6a3af in QEventDispatcherGlib::processEvents ()
   from /usr/lib64/libQtCore.so.4
#39 0x00007f4d2b3ffccf in ?? () from /usr/lib64/libQtGui.so.4
#40 0x00007f4d2ef40782 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#41 0x00007f4d2ef4090d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#42 0x00007f4d2ef42dfd in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#43 0x0000000000404a7b in _start ()
#0  0x00007f4d2974e261 in nanosleep () from /lib64/libc.so.6

Comment 1 edgar klüsener 2008-11-19 11:18:18 UTC

I have disabled all filters, the crashes still occur.

Comment 2 Jaime Torres 2008-11-19 12:10:54 UTC

It looks like you can reproduce the crash. Unfortunately, the backtrace does not contains enough informaion, please look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
and try to post the good backtrace. Thanks for your report.

Comment 3 George Kiagiadakis 2009-01-18 16:21:19 UTC

No information from the reporter for 2 months. Closing. If this crash ever
happens again, please reopen the bug with a better backtrace. Thanks.