Version: (using KDE 4.0.3) Installed from: Ubuntu Packages OS: Linux I've been experiencing this with Kubuntu 8.04 (hardy) since the kde 4.0.2 release. When KDE starts, the logon takes a while, the desktop loads, i can't click on anything and the boot splash stays in middle of screen. Eventually I can click the kickoff button while the splash logo is still in middle of screen. Also, all KDE4 apps take a while to start for the first time. Konqueror, Konsole, and Yakuake kde4 version. KDE3 apps seem to start right up. Even after subsequent reboots same issue persists. I've removed the .kde4 directory, and logged back in, same issue continues.
On Mon, Apr 21, 2008 at 02:54:36PM -0000, Caleb O'Connell wrote: Hej, > I've been experiencing this with Kubuntu 8.04 (hardy) since the kde 4.0.2 release. Work fine with current version (KDE4.1 RC) Ciao, Tobias
No, it doesn't. This issue has been laying around for a very long time now and affects all KDE 4 releases. I usually don't care about login delay as I power up my desktop only once a day, but since I own a notebook I get to see it more often. On my Toshiba Satellite (Centrino 1.6 GHz, 2 GB RAM, fast hard-drive) the boot sequence (from power-on to KDM being ready) is actually shorter than the time KDE needs to log me in. I also tried to empty my .kde directory like Caleb and it doesn't really get faster. I am currently using Ubuntu 9.10 Beta but this issue is much older.
such problems are usually an indicator of a bad dns setup. check how long "host localhost", "host <local net host>", "host google.com", etc. take in all network configs (including none).
To investigate the problem further, you could do the following: Install and configure bootchartd (apt-get install bootchartd bootchart) and prevent that the bootchartd is stopped when kdm is started (for example, by deleting the symlink / etc/rc2.d/S99bootchart => May not work for dependency based boot). Then restart your computer, log into Kde4 and waiting until the system was fully loaded. Then stop bootchartd by /etc/init.d/bootchart start (!). After that you can get an image of the boot process by starting bootchart (!= bootchartd). Of course further investigations are then needed to find the real cause. But it is a start...