Hi folks! I have kde 3.4b1, too and do not have this problem. So I searched for the earlykdm service. I have that, too, but it's not active. So perhaps a simple "insserv -r earlykdm" could fix this? Best, Daniel Am Sonntag, 6. Februar 2005 20:19 schrieb Richard Bos:
Op zondag 6 februari 2005 19:04, schreef Frits Spieker:
I have the feeling that with the current kde 3.4 version X is launched a bit too early. Do others experience the same problem? Is there a solution?
I have exactly the same problem. I believe it has to do with a service called "earlykdm" which is depending on "earlysyslog" and "earlykdb" to be present and running. (but ofcourse, I might be waaayyyy off!)
The new rpm's do install this service earlykdm, but earlykdb and earlysyslog are nowhere to be found.
I too can login to X if I boot into textmode. Trying to login booting into a graphical environment fails as the keyboard stops working. (NUMLOCK goes off as well)
This could well be it, as X seems to be started around 'hardware detection', however at that point still some services are to be started.
-- Richard Bos Without a home the journey is endless