Maybe you should try the option " protect do not change?!
I am going to try it, but not today because yesterday and the day before I was reinstalling SUSE so many times I am tired to do it again now (HI).

Thanks for your replies, the process of rollback a package in SuSE is one thing that I want to do for the future. I'm still wondering how to do it, the SuSE way.

Today I found the solution to this problem:

Just go to YaST -> Refresh your installation sources and then to Software Management, you'll find that kdebase3 and kdebase3-kdm are in color blue, this means that you can update to the packages kdebase3-3.5.1-33 and kdebase-kdm-3.5.1-33!.

I update them, and reboot my system. The process of booting now is working correctly. The bug present in kdebase3-kdm has been eliminated. Thanks to all the SuSE developers. This is one thing that I like about Linux, it took only some days to solve this problem. Nice, very nice!

Can you tell me what you got in your list of installation sources?
I only have kdebase3.5.1-27 in mine.

SUSE LINUX Version 10.0 ftp://mirrors.kernel.org/opensuse/di...SS/inst-source
SUSE LINUX Version 10.0 ftp://mirrors.kernel.org/opensuse/di...st-source-java
SUSE LINUX Version 10.0 ftp://mirrors.kernel.org/suse/i386/1...x10.0-GM-Extra
supplementary KDE 3.5 update ftp://ftp.suse.com/pub/suse/i386/sup....0/yast-source
supplementary GNOME 2.12 update ftp://ftp.suse.com/pub/suse/i386/sup....0/yast-source
guru (SUSE LINUX 10.0) http://ftp.gwdg.de/pub/linux/misc/super-guru/rpm/10.0

Actually, it depends on your architecture, mine is i386. Perhaps you have a different architecture and possibly these packages are not in the repositories yet.

My Kde resource is:

suse.mirrors.tds.net
pub/suse/i386/supplementary/KDE/update_for_10.0/yast-source

I had kdebase3-3.5.1-33 but my kdebase-kdm was kdebase-kdm3-3.5.1-27. Why??? And where can I get kdebase-kdm3-3.5.1-33???

Red Knuckles, make sure that refresh is ON in your installation sources. Then proceed normally with YaST -> Software Management. This package kdebase-kdm3-3.5.1-33 was added today to the repositories. Try again.

I double checked. All repos are enabled and refresh is 'ON' for all. It still isn't making kdebase-kdm3-3.5.1-33 available. I don't get it. Why am I being discriminated against???

Whee Doggiee!! Ride 'em cowboy. Problem solved. It was true for me that installing the packages
kdebase3.3-3.5.1-33 and kdebase-kdm3-3.5.1-33 does solve the problem as victorh says. If for any reason anyone has problems getting both of these packages in your YaST2>Software Management you can get them here:

http://www.novell.com/linux/download...10_0/base.html

I download files of this type to my home folder. Then you just open home folder, right click on the file, select 'Actions>Install with YaST2'. Simple as that!

Well, Red Knuckles I'm sorry that you don't have this package available yet. It's pretty strange since we are using the same repositorie. The only difference is that we are using different mirrors, maybe the mirror that you are using will be updated soon. It should be available, I don't know why you can't update it right now.

i am so there with you, suse hung ever step i took and it seems to be a prob with kde 3.5 KDM. when you isntall that it creates some erroe and all the updated suse`s with kde 3.5 latest all hang, it is mentioned in like 4 other forusma nd threads here.

Victorh, thanks again for the help. As you can see from the above post I did resolve this issue. The packages are available for anyone at:

http://www.novell.com/linux/download...10_0/base.html

Victorh thanks, I did resolve this issue too. Installed the last update of kdebasekdm3 and all is as it should be.

I'm glad you solve the problem, and Happy Birthday riba43!!!

Thank you victorh.
Well, it seems that each day is a year more on my shoulder. Older you are, the quicker the years are passing by.

thank you

hi guys,

I had the same problem after yast update of kde packages. the problem seemed to be a bug in the preload packages. since deleted via rpm the problem was not any more existent. but updating to newer kdebase packages is also a solution. hopefully this helps.