Re: [suse-kde] kde-3.4 beta startup problem
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
Dnia niedziela, 6 lutego 2005 20:19, Richard Bos napisał: Had same problem , but if I change KDM to GDM all its OK Regards
On Sunday 06 February 2005 20:32, Wojciech Paszkowski wrote:
Had same problem , but if I change KDM to GDM all its OK
Does indeed solve the login problem. Only I find that transparency does not work anymore either. Cheers, Frits
On Mon, 7 Feb 2005 18:29:47 +0100, "Frits Spieker"
On Sunday 06 February 2005 20:32, Wojciech Paszkowski wrote:
Had same problem , but if I change KDM to GDM all its OK
Does indeed solve the login problem. Only I find that transparency does not work anymore either.
Cheers, Frits
Sorry for the dumb question, but how do I change from KDM to GDM? Upon the upgrade to 3.4beta1 I no longer have an entry for Gnome in KDM, plus I tend to like GDM better anyway. So maybe I can solve both issues. Thanks. -- Trey Sizemore trey@fastmail.fm
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
Op maandag 7 februari 2005 18:36, schreef Trey Sizemore:
Sorry for the dumb question, but how do I change from KDM to GDM? Upon the upgrade to 3.4beta1 I no longer have an entry for Gnome in KDM, plus I tend to like GDM better anyway. So maybe I can solve both issues.
use yast -> system -> sysconfeditor -> desktop -> desktop manager Somewhere select the desktop manager... -- Richard Bos Without a home the journey is endless
Op maandag 7 februari 2005 18:46, schreef Daniel Eckl:
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?
It was activated and after 'insserv -r earlykdm' it does not blank anymore. However I can still not use the keyboard.... Changed to gdm, it now works again .... -- Richard Bos Without a home the journey is endless
participants (5)
-
Daniel Eckl -
Frits Spieker -
Richard Bos -
Trey Sizemore -
Wojciech Paszkowski