Bug 286 - kmail didn't proceed with getting mail
Summary: kmail didn't proceed with getting mail
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-05 14:14 CET by AL13N
Modified: 2011-07-06 12:29 CEST (History)
3 users (show)

See Also:
Source RPM: kmail
CVE:
Status comment:


Attachments

Description AL13N 2011-03-05 14:14:00 CET
Description of problem:
- kmail showed the page of please wait while getting emails, and didn't proceed
- status bar below showed 0% and clicking on the arrow to see details didn't do anything
- it looked like it was hanging, but menu items were still clickable and stuff
- systray icon had gone, even though there were unread email and it was set to appear as that, on top of closing the app, just seemed to minimize it, starting the app again, made it appear instantly because it was running.
i had to kill it using the ksysguard.

thinking about this now, it may have been the upgrade of KDE to 4.6.1 while it was still opened in systray?

if it is upgrade, is there a way we can restart componenents or advise to re-login?

How reproducible:
- not reproducible



Reproducible: 

Steps to Reproduce:
Comment 1 John Balcaen 2011-03-05 14:33:30 CET
I did not notice this kind of problem during the upgrade here :/

CC: (none) => balcaen.john

Comment 2 Lucien XU 2011-03-11 16:14:12 CET
Cannot reproduce here.
I'm using IMAP and I have also tried the systray icon. I can also close it without killing it.

CC: (none) => sfietkonstantin

Comment 3 D Morgan 2011-04-24 09:19:42 CEST
AL13N, can you test with the beta2 pre release isos ?

CC: (none) => dmorganec

Comment 4 John Balcaen 2011-07-05 15:11:14 CEST
ping ?
Comment 5 AL13N 2011-07-05 21:44:52 CEST
ah yes, i couldn't reproduce it, i had an image, but with beta2 (and later ones) the upgrade size requirements exceeded the disk capacity, after that, i tried to grow the original image, but then i fucked it up, or maybe it was already fucked up from before...

so, yeah, in short i can't reproduce...
Comment 6 John Balcaen 2011-07-06 12:29:51 CEST
Closing as worksforme than.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME


Note You need to log in before you can comment on or make changes to this bug.