[Bug 140667] New: KMail freezes and hogs CPU when failed IMAP authentication is canceled
Marcelo Sales
mmtsales at gmail.com
Fri Jan 26 14:06:19 GMT 2007
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=140667
Summary: KMail freezes and hogs CPU when failed IMAP
authentication is canceled
Product: kmail
Version: 1.9.5
Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs kde org
ReportedBy: mmtsales gmail com
Version: 1.9.5 (using KDE KDE 3.5.5)
Installed from: Fedora RPMs
OS: Linux
When IMAP authentication fails, KMail shows the user/password dialog to let you correct the account info if necessary. If you press "Cancel" in this dialog, KMail freezes and starts to consume 85%-95% of CPU until it's killed. If, instead of pressing the "Cancel" button, you try to authenticate again, KMail becomes usable for some seconds until the authentication fails another time and the account info dialog is shown again. This can be repeated indefinitely.
KMail tries to authenticate in the IMAP server even if the "Check mail in initialization" checkbox in accounts configuration is not checked. Because of this behavior and the "Cancel" bug described above, it's impossible to use KMail if there's a problem with a configured IMAP account.
Steps to reproduce the bug:
1. Configure an IMAP account in KMail, but fill in the password field with a wrong value
2. Close KMail
3. Open KMail. The IMAP account authentication will fail and the user/password dialog will be shown. Other KMail windows will be unusable while this modal dialog is shown (which is ok).
4. Try to authenticate again with a wrong password. KMail will become usable for seconds before the authentication fails again.
5. Now click Cancel in the user/password dialog. The dialog goes away, but KMail remains unusable. No widgets in any opened kmail windows respond to mouse clicks. No keyboard shortcut works. Open ksysguard and note that KMail process is using 85%-95% of CPU. It remains like that until you kill the process.
Don't know if this is important, but I usually run KMail in Kontact.
More information about the Kdepim-bugs
mailing list