Bug 154688

Summary:	kmail crashes
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Andreas Kleen <ak>
Component:	KDE	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P3 - Medium	CC:	asklein, suse-beta, vetter
Version:	Beta 4
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Andreas Kleen 2006-03-02 13:16:41 UTC

Got this crash several times now while using imap. Kmail tells me 
"The connection to server ... has unexpectedly closed" and then
it segfaults. The backtrace is:

System configuration startup check disabled.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(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 -1247200720 (LWP 3436)]
[New Thread -1276732512 (LWP 3453)]
[New Thread -1268339808 (LWP 3452)]
[New Thread -1259947104 (LWP 3451)]
[New Thread -1251554400 (LWP 3450)]
(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)
[KCrash handler]
#6  0xb6a5872a in KPIM::ProgressItem::setComplete ()
   from /opt/kde3/lib/libkdepim.so.1
#7  0xb7d87aeb in KMail::ImapAccountBase::removeJob ()
   from /opt/kde3/lib/libkmailprivate.so
#8  0xb7ec236f in KMFolderImap::slotListFolderResult ()
   from /opt/kde3/lib/libkmailprivate.so
#9  0xb7ec34ba in KMFolderImap::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so
#10 0xb73eeb7d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb64416de in KIO::Job::result () from /opt/kde3/lib/libkio.so.4
#12 0xb648583d in KIO::Job::emitResult () from /opt/kde3/lib/libkio.so.4
#13 0xb649a0ce in KIO::SimpleJob::slotFinished ()
   from /opt/kde3/lib/libkio.so.4
#14 0xb649a45d in KIO::ListJob::slotFinished () from /opt/kde3/lib/libkio.so.4
#15 0xb6470233 in KIO::SimpleJob::slotError () from /opt/kde3/lib/libkio.so.4
#16 0xb6485313 in KIO::SimpleJob::qt_invoke () from /opt/kde3/lib/libkio.so.4
#17 0xb649c2d3 in KIO::ListJob::qt_invoke () from /opt/kde3/lib/libkio.so.4
#18 0xb73eeae1 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb6443130 in KIO::SlaveInterface::error () from /opt/kde3/lib/libkio.so.4
#20 0xb64a4f80 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#21 0xb64ae2aa in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#22 0xb645100c in KIO::Slave::gotInput () from /opt/kde3/lib/libkio.so.4
#23 0xb649e5e0 in KIO::Slave::qt_invoke () from /opt/kde3/lib/libkio.so.4
#24 0xb73eeb7d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb73ef242 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb772d960 in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0xb740cc10 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb738f6f7 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb73903c1 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0xb7a514a3 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#31 0xb7384214 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb733e9a4 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb73a6448 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb73a62de in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0xb738f18f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0x0804a0cd in ?? ()
#37 0xbf91af84 in ?? ()
#38 0xbf91b170 in ?? ()
#39 0x00000000 in ?? ()

Comment 1 Stephan Kulow 2006-03-02 13:35:26 UTC

http://bugs.kde.org/show_bug.cgi?id=88949 - reported for 3.3.2
http://bugs.kde.org/show_bug.cgi?id=101814 - reported for 3.4.0
http://bugs.kde.org/show_bug.cgi?id=114953 - reported for 3.5 beta2

Pretty much unreproducible (using kmail all day myself) ;(

If you think you can reproduce this in your setup, please install debuginfo package for kdepim3 and try valgrind. There is little hope otherwise ;(

Comment 2 Andreas Kleen 2006-03-02 13:38:43 UTC

I didn't see it in earlier KDE release.

It might be related to the connection to the server being flakey. I'm not local
and there is sometimes packet loss talking to the suse imap server.

I can try valgrind but i'll be likely painful because I would need to use
it like this for a longer time :/

And where can I find the debuginfos for beta4?

Comment 3 Andreas Kleen 2006-03-02 13:39:27 UTC

P.S.  a way to simulate a flakey server would be to occasionally pull your
ethernet cable.

Comment 4 Stephan Kulow 2006-03-02 13:46:27 UTC

I doubt you'll be able to get beta4 debuginfos yet. But you should be able to update kdepim3 from stable + it's debuginfo files. 

And for #3: if I pull my ethernet cable, I loose my home directory and will see different bugs ;)

Comment 5 Andreas Kleen 2006-03-02 13:49:15 UTC

debuginfos from stable: Ok i will try that. Might take some time.

Then use iptables to block the imap port temporarily.

Comment 6 Stephan Kulow 2006-03-02 17:38:36 UTC

I was unable to reproduce "... has unexpectedly closed" with iptables ;(

Comment 7 Stephan Kulow 2006-03-03 15:10:15 UTC

I might try later again, if I can reproduce this. But as long as it only hits in very specific network setups, I see little hope ;(

Comment 8 Harald Mueller-Ney 2006-04-23 06:05:29 UTC

Status?
Andi, have you had time to reproduce?

Comment 9 Dirk Mueller 2006-05-04 13:44:46 UTC

still no lock with reproducing here? can you trigger it reliably?

Comment 10 Andreas Kleen 2006-05-04 17:35:57 UTC

I think it always happened when my DSL connection lost the IP address (and 
connections timed out etc.)  Haven't used 10.1 kmail much recently.

Comment 11 Stephan Kulow 2006-10-27 13:22:39 UTC

this bug is just bit roting I'm afraid