[opensuse] kdm starts twice, not good
I seem to have got myself to a situation where kdm shows itself in the tty1 console as starting twice at boot into runlevel 5. The outcome is a solid freeze, usually sooner rather than later, requiring a reset. If I boot to runlevel 3 and call kdm from the tty1 console, all is fine I have done a little 'print' debugging and found that K15xdm gets called twice, I think as part of runlevel change. Can anyone point me to a good resource which will help me trace through the process of changing to runlevel 5, and get to the bottom of the problem? Using boxed opensuse 10.2, AMD 64 bit with dual opterons and a matrox g450, FWIW - I am more inclined to think it is to do with fiddling with the /etc/sysconfig editor and inadvertently changing things. Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-05-01 at 20:13 +0100, Vince L wrote:
I seem to have got myself to a situation where kdm shows itself in the tty1 console as starting twice at boot into runlevel 5. The outcome is a solid freeze, usually sooner rather than later, requiring a reset. If I boot to runlevel 3 and call kdm from the tty1 console, all is fine
I have done a little 'print' debugging and found that K15xdm gets called twice, I think as part of runlevel change. Can anyone point me to a good resource which will help me trace through the process of changing to runlevel 5, and get to the bottom of the problem?
man init.d and a very good writeup in the suse admin book, that now has another name and no longer comes in paper. The chapter may be named something like "INIT.D - The SuSE boot concept". Have a look at "/etc/init.d/rc5.d/", see if there are two "S*xdm" files, and inside the "/etc/init.d/.depend.start" file.
Using boxed opensuse 10.2, AMD 64 bit with dual opterons and a matrox g450, FWIW - I am more inclined to think it is to do with fiddling with the /etc/sysconfig editor and inadvertently changing things.
Could be... but I don't know how. Have a look at "/etc/sysconfig/displaymanager". - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGOGqGtTMYHG2NR9URAgJbAJ45jbQl5GtmNm+S5uCGkjyZCDQm1gCfZJOf F5hgvkBTyMRKPH72SiO4sF0= =shwu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
If you have a KDE Desktop open Control Centre>KDE Components>KDE Performance check the value in Preload an Instance after KDE startup AND Maximum number of instances kept preloaded Hope this helps - Scott Vince L wrote:
I seem to have got myself to a situation where kdm shows itself in the tty1 console as starting twice at boot into runlevel 5. The outcome is a solid freeze, usually sooner rather than later, requiring a reset. If I boot to runlevel 3 and call kdm from the tty1 console, all is fine
I have done a little 'print' debugging and found that K15xdm gets called twice, I think as part of runlevel change. Can anyone point me to a good resource which will help me trace through the process of changing to runlevel 5, and get to the bottom of the problem?
Using boxed opensuse 10.2, AMD 64 bit with dual opterons and a matrox g450, FWIW - I am more inclined to think it is to do with fiddling with the /etc/sysconfig editor and inadvertently changing things.
Thanks
participants (3)
-
Carlos E. R.
-
Registration Account
-
Vince L