Bug 124295

Summary: kmail startup takes 20sec
Product: [Unmaintained] kmail Reporter: Imre Péntek <pentek.imre>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version First Reported In: 1.9.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: kolourpaint output

Description Imre Péntek 2006-03-26 15:00:57 UTC 
Version:           1.9.1 (using KDE KDE 3.5.1)
Installed from:    Unlisted Binary Package
Compiler:          gcc version 3.4.5 Configured with: /var/uhubuild/work/compile/configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++ --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --host=i586-uhu-linux; Thread model: posix
OS:                Linux

kmail startup sometimes takes at least 20sec, but inside this 20sec period there is a 10sec gap, where processor usage is ~0%. I think it should be faster.
Comment 1 Philip Rodrigues 2006-03-26 22:53:23 UTC 
Do any other KDE apps show similar behaviour? Problems like this can be caused by incorrect network settings.
Comment 2 Imre Péntek 2006-03-26 23:02:59 UTC 
As I see no other apps do the same I suspect that some race condition is occuring between accidentally launched multiple kmail processes (https://bugs.freedesktop.org/show_bug.cgi?id=5765).
Comment 3 Philip Rodrigues 2006-03-27 18:19:14 UTC 
Sounds plausible. Can you try starting kmail using something other than the multimedia keys, so you can confirm your hypothesis?
Comment 4 Imre Péntek 2006-03-27 19:28:14 UTC 
Well, my current results seem to ruin the expectation, I rebooted my computer, started IceWM, xterm, and launched one istance of kmail by typing kmail and hitting enter. The startup was as slow as launching kmail by the multimedia key, with the no-cpu-load present as in the previous case.
Comment 5 Imre Péntek 2006-07-28 05:33:07 UTC 
Still present in 1.9.3 kde 3.5.3.
Comment 6 Ingo Klöcker 2006-07-28 10:07:10 UTC 
Does KMail probably wait for responses of servers? If you enabled fetching mail on startup then KMail will check for new mail before the window appears. Depending on the number of accounts KMail has to check this might of course take some time, especially with IMAP accounts. And while KMail waits for a server's response it does of course not use any CPU.

Please try whether disabling "Check mail on startup" helps.
Comment 7 Imre Péntek 2006-07-29 19:45:44 UTC 
If you enabled fetching mail on startup then KMail will check for new mail _after_ the window appears. As I see. I will test with "Check mail on startup" disabled.
It will take long time.
Comment 8 Imre Péntek 2006-07-30 17:24:00 UTC 
I found that 20sec gap in the startup of kolourpaint too. Maybe it is just present at the first startup of a kde process after reboot (I use IceWM). I will attach output.
Comment 9 Imre Péntek 2006-07-30 17:25:32 UTC 
Created attachment 17171 [details]
kolourpaint output
Comment 10 Ingo Klöcker 2006-07-30 22:25:54 UTC 
That does explain your observation. If you start the first KDE apps then a lot of KDE services need to be started and initialized. Since the services are automatically shutdown when you close this KDE app the next start of a KDE app will again take some time.

I hope it's okay that I close your report.