Bug 136545

Summary:	Reproducible Deadlock in KMail
Product:	[Unmaintained] kmail	Reporter:	min <mihnea_capraru>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	bjoern
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	FreeBSD Ports
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description min 2006-10-31 02:48:19 UTC

Version:            (using KDE KDE 3.5.4)
Installed from:    FreeBSD Ports

Note: this is actually a freeze, not literally a crash, but they're to the same effect anyway.

To make KMail (or Kontact) deadlock (or at any rate freeze), follow these steps:

- configure an online IMAP account with a wrong password

- tell KMail to check the account on startup

- restart KMail (this is manadatory)

- the "please enter the correct password" dialog comes up

- hit cancel

- KMail will never come back.

BTW, there's another issue with endless dialog-cancel-dialog loops when unable to connect to IMAP accounts, very often reported, maybe they're related to this issue.

Comment 1 Bram Schoenmakers 2006-10-31 15:21:56 UTC

What do you mean exactly with "KMail will never come back?" The screen is not repainted, but remains a gray/white surface without text (and the CPU goes like 100%)? In that case, this is a different bug than the many-reported-infinite-loop with IMAP authentication (bug 122096).

Comment 2 min 2006-10-31 18:26:25 UTC

> What do you mean exactly with "KMail will never come
> back?" The screen is not repainted, but remains a
> gray/white surface without text 


Right.

> (and the CPU goes
> like 100%)? In that case, this is a different bug
> than the many-reported-infinite-loop with IMAP
> authentication (bug 122096).


It's certainly different, I was just suggesting that
they might have the same cause. 





	
		
___________________________________________________________ 
Der fr

Comment 3 Philip Rodrigues 2006-11-01 00:15:21 UTC

When KMail freezes, try killing it with "kill -SEGV <pid-of-kmail>". That might get you a crash dialog with  backtrace. If so, please paste the backtrace here, thanks.

Comment 4 min 2006-11-01 13:17:40 UTC

[New Thread 0x8341000 (sleeping)]
[New Thread 0x8330e00 (sleeping)]
[New Thread 0x8330c00 (sleeping)]
[New Thread 0x8330a00 (sleeping)]
[New Thread 0x8330800 (LWP 100174)]
[New Thread 0x8055000 (LWP 100170)]
[Switching to Thread 0x8055000 (LWP 100170)]
0x2a24199f in QString::operator+= () from /usr/X11R6/lib/libqt-mt.so.3
#0  0x2a24199f in QString::operator+= () from /usr/X11R6/lib/libqt-mt.so.3
#1  0x2825ed85 in KMAccount::encryptStr ()
   from /usr/local/lib/libkmailprivate.so
#2  0x28331aca in KMail::NetworkAccount::passwd ()
   from /usr/local/lib/libkmailprivate.so
#3  0x2833acb6 in KMail::ImapAccountBase::makeConnection ()
   from /usr/local/lib/libkmailprivate.so
#4  0x28343c1b in KMAcctImap::makeConnection ()
   from /usr/local/lib/libkmailprivate.so
#5  0x28363be6 in KMFolderImap::slotListNamespaces ()
   from /usr/local/lib/libkmailprivate.so
#6  0x28364d9c in KMFolderImap::qt_invoke ()
   from /usr/local/lib/libkmailprivate.so
#7  0x29f58cbd in QObject::activate_signal ()
   from /usr/X11R6/lib/libqt-mt.so.3
#8  0x28334ab9 in KMail::ImapAccountBase::connectionResult ()
   from /usr/local/lib/libkmailprivate.so
#9  0x2833abf4 in KMail::ImapAccountBase::makeConnection ()
   from /usr/local/lib/libkmailprivate.so
#10 0x2833b7e5 in KMail::ImapAccountBase::slotSchedulerSlaveError ()
   from /usr/local/lib/libkmailprivate.so
#11 0x28340344 in KMail::ImapAccountBase::qt_invoke ()
   from /usr/local/lib/libkmailprivate.so
#12 0x28347773 in KMAcctImap::qt_invoke ()
   from /usr/local/lib/libkmailprivate.so
#13 0x29f58d34 in QObject::activate_signal ()
   from /usr/X11R6/lib/libqt-mt.so.3
#14 0x293a7617 in KIO::Scheduler::slaveError ()
   from /usr/local/lib/libkio.so.6
#15 0x293a8d04 in KIO::Scheduler::slotSlaveError ()
   from /usr/local/lib/libkio.so.6
#16 0x293ac32f in KIO::Scheduler::qt_invoke () from /usr/local/lib/libkio.so.6
#17 0x29f58d34 in QObject::activate_signal ()
   from /usr/X11R6/lib/libqt-mt.so.3
#18 0x293a1c9c in KIO::SlaveInterface::error ()
   from /usr/local/lib/libkio.so.6
#19 0x293a48c4 in KIO::SlaveInterface::dispatch ()
   from /usr/local/lib/libkio.so.6
#20 0x293a32e3 in KIO::SlaveInterface::dispatch ()
   from /usr/local/lib/libkio.so.6
#21 0x2939f06b in KIO::Slave::gotInput () from /usr/local/lib/libkio.so.6
#22 0x2939f428 in KIO::Slave::qt_invoke () from /usr/local/lib/libkio.so.6
#23 0x29f58d34 in QObject::activate_signal ()
   from /usr/X11R6/lib/libqt-mt.so.3
#24 0x29f592fa in QObject::activate_signal ()
   from /usr/X11R6/lib/libqt-mt.so.3
#25 0x2a2ae780 in QSocketNotifier::activated ()
   from /usr/X11R6/lib/libqt-mt.so.3
#26 0x29f7570f in QSocketNotifier::event () from /usr/X11R6/lib/libqt-mt.so.3
#27 0x29ef4b3f in QApplication::internalNotify ()
   from /usr/X11R6/lib/libqt-mt.so.3
#28 0x29ef4cdc in QApplication::notify () from /usr/X11R6/lib/libqt-mt.so.3
#29 0x299a0f98 in KApplication::notify () from /usr/local/lib/libkdecore.so.6
#30 0x29ee8454 in QEventLoop::activateSocketNotifiers ()
   from /usr/X11R6/lib/libqt-mt.so.3
#31 0x29ea01ec in QEventLoop::processEvents ()
   from /usr/X11R6/lib/libqt-mt.so.3
#32 0x29f0b282 in QEventLoop::enterLoop () from /usr/X11R6/lib/libqt-mt.so.3
#33 0x29f0b1d6 in QEventLoop::exec () from /usr/X11R6/lib/libqt-mt.so.3
#34 0x29ef3cef in QApplication::exec () from /usr/X11R6/lib/libqt-mt.so.3
#35 0x0804a666 in main ()

Comment 5 Björn Ruberg 2009-12-30 18:02:34 UTC

Is this still happening with KDE 4.3?

Comment 6 Björn Ruberg 2010-04-06 00:32:25 UTC

No response. Closing old KDE 3 crash