Bug 94565 - GUI modal popup deadlock on IMAP server connection error
Summary: GUI modal popup deadlock on IMAP server connection error
Status: RESOLVED DUPLICATE of bug 94168
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-06 22:32 UTC by Patrick Bellasi
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Bellasi 2004-12-06 22:32:02 UTC 
Version:            (using KDE KDE 3.3.1)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6) 
OS:                Linux

When I click on an IMAP account and the connection to the IMAP server fails an error popup is showen saying:

Error - Kontact
Could not connect to host <host§_FQDN>
OK

This popup is MODAL and if I click OK... It simply appear again and again... till, I hope, the connection to the server is ok...
but every time I have to kill kontact to soleve the GUI "DEADLOCK"

I've reproduced the BUG by simply stopping my net just after starting Kontact and befor clicking on my IMAP account.

The problem may be due to the fact that the focus remain to the same IMAP account after I respond OK to the popup... and so the endless loop of error popups!
Comment 1 Patrick 2006-10-28 14:37:59 UTC 
Works for me. I just get one error message each time when I click on a folder which belongs to the unreachable imap server. No GUI deadlock whatsoever.
Comment 2 Anne-Marie Mahfouf 2006-10-28 14:40:41 UTC 
*** Bug has been marked as fixed ***.
Comment 3 Will Stephenson 2006-10-28 22:06:27 UTC 
Actually this can still happen in other circumstances, eg no auth method for server.
Comment 4 Will Stephenson 2006-10-28 22:07:41 UTC 

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