Bug 69379 - JJ: make IMAP error messages KQueuedMessageBoxes
Summary: JJ: make IMAP error messages KQueuedMessageBoxes
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Unmaintained
Component: IMAP (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2003-11-30 18:55 UTC by Otto Bruggeman
Modified: 2008-11-23 21:20 UTC (History)
1 user (show)

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 Otto Bruggeman 2003-11-30 18:55:21 UTC 
Version:            (using KDE KDE 3.1.94)
Installed from:    Compiled From Sources
Compiler:          g++ 3.3.1 The SuSE 9.0 g++
OS:          Linux

I was having some server problems after an upgrade from SuSE 8.2 to 9.0. One of the problems was that i did not have imaps set up properly, so KMail gave me an error message everytime i selected a message. After i click the message away the mouse pointer turns into a circle with a / in it (don't know the name of that cursor) as soon as i move the mouse back into the kmheaders widget. I think it is used to indicate you cant drag a message to that location. Hope this is enough to fix the bug :) Thanks for a great mua guys !
Comment 1 Ingo Klöcker 2003-12-01 10:58:51 UTC 
The error messages should be made queuedMessageBoxes so that they don't block the program flow. There's no reason to block it.
Comment 2 Alexander Egger 2007-12-15 21:04:04 UTC 
While this bug still exists in 1.9.6 it seams to have disappeared in the svn trunk version (after KDE 4 RC2).
Comment 3 Fernando Vilas 2008-11-09 19:21:10 UTC 
I shutdown the VPN to my IMAP server and tried to select a message.  KMail complains about not being able to contact the server, but the cursor does not change as described.  
Tested on KMail 1.10.1.
Comment 4 Michael Leupold 2008-11-23 21:20:07 UTC 
I can't reproduce this bug either using trunk r887937. Closing.