Suse 12.3: Lost kde at startup

Hello All,

I just update my system to Suse 12.3 and KDE 4.10.
During the upgrading I made a mistake, I had the nVidia repository deactivated, so after the first run the system didn’t start correctly.
I had to boot in console mode, activate the nVidia repository and update it.
Now, when I start the computer, it starts in console mode, and so I have to give the startkde command each time to run KDE. After that, the system works fine.

I tried to see if there was something wrong in the /etc/conf/displaymanager, but it looks right to me, here below the relevant lines:

DISPLAYMANAGER_RANDR_MODE_auto="1024x768_60 64.11 1024 1080 1184 1344 768 769 772 795 -HSync +Vsync"

Any idea on how to have KDE starting automatically at boot again?

I opened YaST and sysconfig editor and i see the following . Probably displaymanager should be kdm4. Then again i might be wrong

File:  /etc/sysconfig/displaymanager
Possible Values:  kdm, kdm3, kdm4, xdm, gdm, wdm, entrance, console or any value
Default Value:  

Here you can set the default Display manager (kdm/xdm/gdm/wdm/entrance/console).
all changes in this file require a restart of the displaymanager

Thanks for the suggestion, I tried that, but it didn’t work.

Login as root using the following steps:

Type in: su - systemctl isolate


Type in: su - systemctl isolate

BTW the display manager is kdm.
And select DISPLAYMANAGER_AUTOLOGIN=yourusername which can be found in /etc/sysconfig/Desktop/Display manager/DISPLAYMANAGER_AUTOLOGIN=yourusername

Hope this is also set correctly

File:  /etc/sysconfig/windowmanager
Possible Values:  gnome, kde4, kde, lxde, xfce, twm, icewm or any value
Default Value:  kde4

The command “su - systemctl isolate” (without the quotes) is used to get to the gui desktop.

If it doesn’t work and if it’s a fresh install including the /home partition use “rm -rf .kde4” (without quote) to delete it.

Reboot your computer. During start up a new .kde4 will be regenerated.

We value your contributions, but can you please put CODE tags around the commands you offer to be used? That will clearly make a boundary between what you tell and the commands themselves and make them better readable (while reading normal language the difference between l I and 1 might not put anybody on the wrong leg, but in commands it may be fatal).

You get the CODE tags by clicking on the # button in the toolbar of the post editor.

Thank you in advance.

Sorry for the late response, but yes, the method suggested by Romanator actually worked.

Thanks to everybody for suggestions!