I installed the (unsupported) suse kde-3.4 beta rpms, and I experience a problem with this. The problem is something with X, at the point were the latter is being started. Today I experienced that X got displayed at VT2 (virtual terminal) instead of VT7. After some time (15-30 seconds) the screen became blank (black). It was possible to swap between VT1 and VT2, that was about it. Another time, same system, it continued in X, but than I could not use my keyboard (mouse is okay). The big mystery begins: when I set the default init level to 3 and login as root after boot and execute an init 5, all is working well.... :)) 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? -- Richard Bos Without a home the journey is endless
On Sunday 06 February 2005 18:56, Richard Bos wrote:
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 of course, 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) Grtz, Frits
participants (2)
-
Frits Spieker
-
Richard Bos