Bug 19349 – kdm_greet take a very long time to start up and kde is killed on slow machines

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Andrea Barisani (RETIRED) 2003-04-15 04:32:48 UTC]

Hi 
 
I beleive that I'm seeing bug #15188 with kde-3.1.1a, since the upgrade from 
kde-3.1.1-r1 to kde-3.1.1-a my slow machines (P1 MMX 266, 64 Mb ram) can't start kde 
(kdeinit it's killed by the scheduler) and kdm_greet is very slow to restart (1 or 2 
minutes) and it eats all my swap. The same problem doesn't appear on P4 and k6. 
 
I've search some debugging info but all I can find are Out of memory messages and 
some secondary error in /var/log/kdm.log (can't find kdmdesktop).  
 
What it can be? 
 
Bye 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Andrea Barisani (RETIRED) 2003-04-15 05:31:02 UTC]

Ok, I've tried reemerging kdebase-3.1.1-r1 but the problem remains, so I suppose 
that's a problem with the new qt (I've also updated to qt 3.1.2 at the same time).  
 
I've noticed that since the upgrade the kdm fonts are anti-aliased, who's 
responsible for this? Qt?  

[Comment 2 Andrea Barisani (RETIRED) 2003-04-15 06:53:53 UTC]

Ok, here's more info: 
 
ps aux|grep kdm on P1 64MB ram: 
 
root      8541 15.6 36.4 103824 22888 ?      S    12:45   0:35 
/usr/kde/3.1/bin/kdm_greet 
 
ps aux|grep kdm on k6 128MB ram:  
 
root      6962  0.0  8.6 18864 11020 ?       S    12:23   0:01 
/usr/kde/3.1/bin/kdm_greet 
 
There's something wrong here I suppose. The p1 and k6 configurations are 
identical, same packages, same emerging order, the only differences are CFLAGS: 
 
CFLAGS="-march=pentium-mmx -O3 -pipe" 
 
CFLAGS="-march=k6 -O3 -pipe" 
 
Kde, qt, xft and truetype are all at the latest stable portage version (emerge -u 
--deep world). The fonts are exactly the same on the two hosts. 
 

[Comment 3 Georg Müller 2003-04-15 07:08:57 UTC]

your problem with the startup time should be solved by typing
"fc-cache -f"
to renew the font cache...
That worked for me

[Comment 4 Andrea Barisani (RETIRED) 2003-04-15 07:47:02 UTC]

yes, problem solved! :) (however I've got to reboot all hosts in single mode 
because fc-cache -f eats a lot of swap too) 
 
Thanks a lot :) 
 
P.S. 
I suppose that this sould be documented somewhere, if it's already forgive me for 
my ignorance ;) 

[Comment 5 Paul de Vrieze (RETIRED) 2003-04-24 14:53:56 UTC]

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