I have SuSE 8.0 and am running KDE 3.1 (from the RPMs that I downloaded from suse). I wanted to create myself a new account on my machine so I logged in as root in KDE (I know it has been recommended to never login as root in X, but I just wanted to see what it would break). I created myself the new account that I wanted and checked the hidden option so that it would not appear in kdm listed users. When I rebooted, KDM now has all sorts of different icons for every possible user on the system. Further, when I login using KDM, I don't get a window manager running. All I get is a blue screen on top of which a unix shell is running. There are no Window borders for me to click on. None of the KDE stuff is running. I can start kicker manually by typing kicker on the prompt---which brings up kicker. Then I can run an application but all applications appear in some place without any window borders for me to click on. I cannot even move windows around with a mouse. I have a temporary solution to this. I logged in as su. Then I typed init 3. After this, I use one of my user accounts to log into the machine. When I type startx, everything is working fine. So bottom line---Keeping the run level 3 and startx'ing manually works fine. KDM is broken. I tried re-installing the kdebase package but that didn't help. I also ran SuSEconfig after re-installing, but no help :-( Salman
On Monday 17 February 2003 02:01, Salman Khilji wrote:
So bottom line---Keeping the run level 3 and startx'ing manually works fine. KDM is broken. I tried re-installing the kdebase package but that didn't help. I also ran SuSEconfig after re-installing, but no help :-(
Salman: It may not be a KDM problem. Try setting acpi and apm to off in the Grub menu.lst. That stopped me for a while with the same symptoms as you have. We were using an Nvidia video card which apparently choked. The only adverse action after turning them off is the machine reaches level 0 and does not turn off the power. But that I can live with. Richard
On Monday 17 February 2003 08:01, Salman Khilji wrote:
I have SuSE 8.0 and am running KDE 3.1 (from the RPMs that I downloaded from suse).
I wanted to create myself a new account on my machine so I logged in as root in KDE (I know it has been recommended to never login as root in X, but I just wanted to see what it would break).
I suppose we know now ... yes kids, the old bores who keep saying 'don't log in as root' say it for a reason ...
I created myself the new account that I wanted and checked the hidden option so that it would not appear in kdm listed users.
When I rebooted, KDM now has all sorts of different icons for every possible user on the system. Further, when I login using KDM, I don't get a window manager running. All I get is a blue screen on top of which a unix shell is running. There are no Window borders for me to click on. None of the KDE stuff is running. I can start kicker manually by typing kicker on the prompt---which brings up kicker. Then I can run an application but all applications appear in some place without any window borders for me to click on. I cannot even move windows around with a mouse.
I have a temporary solution to this. I logged in as su. Then I typed init 3. After this, I use one of my user accounts to log into the machine. When I type startx, everything is working fine.
So bottom line---Keeping the run level 3 and startx'ing manually works fine. KDM is broken. I tried re-installing the kdebase package but that didn't help. I also ran SuSEconfig after re-installing, but no help :-(
Salman
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Salman Khilji wrote:
So bottom line---Keeping the run level 3 and startx'ing manually works fine. KDM is broken. I tried re-installing the kdebase package but that didn't help. I also ran SuSEconfig after re-installing, but no help :-(
Salman
It was the fact that during the last settings change to kdm, kde hung up. So I had to basically turn the power off and back on. Well this corrupted my kdmrc file. There were two kdmrc files----one somewhere under /etc/ and the other somewhere under /opt/kde3 I ended up copying the one from the location that wasn't being used to the one that does. kdm is fine now. BTW, in the past logging on as root into KDE would very consistently break your 'kdesu konqueror'. This problem seems to have been fixed in 3.1 Salman
participants (3)
-
Fergus Wilde
-
Richard Atcheson
-
Salman Khilji