when users login in kde4 it shows kstartconf4 not found or failed error code 127…
for both suse 11. 1 and suse 11.2
but kde3 works well
I removed .kde etc it still failed
For KDE 4 it is ~/.kde4, not ~/.kde.
Never log in as root, even not to try these sorts of things. Rather create new user for the test. Such a user. with whatever you tested and did to his files, can easily be removed with all the files.
I did try an user ‘test’ (removing .kde .kde4) but it still failed.
Please try to explain a little bit more.
Do you have two systems, one with 11.1 and the other with 11.2 having the same problem?
Did you mix repositories?
Was this always (from install) or since X-mass, or since an update?
And all sorts of other explanations you forgot to tell, thinking that we know how your shop is running.
Thanks.
For One station 11.1 was installed last year. I selected kde3.5 as default.
However, I found kde4 was installed too. I used the kde3.5 since then.
For the second station 11.2 was installed. KDE was selected. When login as root, it is ok . But when any users tried to login, it shows
:" kstart4conf not found or failed error code 127 check installation".
We have 6 users including “test” . All of them encountered the same trouble.
I checked the station one finding it has kde4. I tested and found the exact same error messages. I don’t like gnome who works well and tried to install the kde3.5 that works fine.
Here, other groups all installed suse (from 10.1 to 11.2). KDE4 seems very troublesome.
A lot of people here, who are normaly willling to help, will refrain from doing so when you state that you (when I interprete correct, even more or less “usually”) log in as root. The reason being that, when you do that, everything can have happend to the system and who is to find out how to remedy this?
Also the fact that (and you know this, because you have of course searched these forums before posting) your problem is encountered by nobody here, leads me to the conclusion that you broke your system. And that can only be done being root.
If I were you, I should wait for a day or so if somebody comes to a (for you) more enjoyable conclusion.