No graphical login screen after updating to SuSE 11.0

[bolkedebeer]

I just updated my Medion Titatnium MD8083 PC with SuSe 10.0 to Suse 11.0 with the DVD iso image i downloaded from opensuse.org.

After running through the entire updating procedure without any problems, on reboot it stopped at initlevel 5, but with just a command line logon prompt!

The last notification I got was:

Master Resource Control: runlevel 5 has been reached
Failed services in runlevel 5: network
Skipped services in runlevel 5: smbfs splash
<notice>killproc: kill(1929,3)


I can logon as root at the command prompt and run startx, and voila, there is KDE. However, if I log on as me and run startx, it gives a lot of errors and is not able to start x.

Does anybody know how I can get the logon screen after booting???

[daark.child]

You need to post the exact errors that you are getting in order for someone to help you.

[gogalthorp]

My guess is you installed KDE 4

KDE 4 is a large change you may need to rename or delete the old ~/.kde directory so a new one with the new settings can be created. You can salvage any custom wallpapers etc from the old .kde directory. Note the period in front of kde.

note ~ is short hand for the current users home directory.

It was probably a bad idea to upgrade you should have done a fresh install and simply not formated the home partition.

There may be other config files that are preserved form the old install and not correct for the new one. It is always better to zap the old root partition and do a fresh install and simply tell the installer to not format the home partition just mount it as /home.

[bolkedebeer]

I really don't know whether I installed kde3 or kde4, after running startx it looks very much the same as it did in SuSe 10.0.

Does the choice of kde really affects not getting a login screen? I thought kde was only started after logging on?

However I will move /root/.kde to /root/.kdeold

It probably was better to really do a new install, but I have only one large physical unix partition, containing both /root and /home. So only formatting /root seems impossible to me.

[bolkedebeer]

You need to post the exact errors that you are getting in order for someone to help you.

That's the point, in the long /var/log/boot.msg only the Firewall seems to have a few problems:

Starting Firewall Initialization (phase 2 of 2) SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
WARNING: module 'nf_conntrack_ipv4' is unsupported
FATAL: Module ip_conntrack not found.
SuSEfirewall2: Warning: FW_ALLOW_INCOMING_HIGHPORTS_UDP=DNS is no longer supported
commit failed on table filter: Invalid argument
SuSEfirewall2: Error: ip6tables-batch failed, re-running using ip6tables
ip6tables: Invalid argument
ip6tables: Invalid argument
done
ip6tables: Invalid argument
ip6tables: Invalid argument
ip6tables: Invalid argument
done
Master Resource Control: runlevel 5 has been reached
Failed services in runlevel 5: network
Skipped services in runlevel 5: smbfs splash
<notice>killproc: kill(1929,3)

[gogalthorp]

I really don't know whether I installed kde3 or kde4, after running startx it looks very much the same as it did in SuSe 10.0.

Does the choice of kde really affects not getting a login screen? I thought kde was only started after logging on?

However I will move /root/.kde to /root/.kdeold

It probably was better to really do a new install, but I have only one large physical unix partition, containing both /root and /home. So only formatting /root seems impossible to me.

In your case since you have a only one partition you had no choice if you wanted to save your home. The problem is that 10 to 11 is a big jump with many things changed. An upgrade preserves the settings and config files from the old install and there may not be compatible to the new version of various programs. Your absolute best bet is to backup the home partition to another drive or some other media. Then install 11 from scratch being sure that home has its own partition so you don't run into this in the future.

Even if you fix the firewall problem there may well be other problems lurking due to incompatible configurations.

[bolkedebeer]

Thanks for the help Gogalthorp.

I tried to remove the .kde file and reinstall kde, however it did not work...

I'm a bit affraid of creating a new partition and then do a full install, but it might be the best course of action I'm always fearing my windows partions or the boot files may be damaged (that happened to me in the past)

Maybe you could think of a less rigorous thing to do? I saw solution like removing all .files, etc.

It seems to me like some xdm or xorg thing, but I cannot figure out what...

[gogalthorp]

This seems like a problem that happens before the user is loaded so deleting user level config files is probably not the answer. You can try it.

Copy /home to the windows partition

Install again being careful around the partitioning so that it only makes (formats) the swap and root and does not try to make a home partition.

Once installed copy home back from the Windows side.