thanks so much to both of you for the detailed how to. It really helps newbs like me out.. I surely appreciate it

I tried your excellently detailed instructions, but as i click asccept the update just seems to quit.. also in viewing the updates.. i don't see any listing for 3.2 only 3.14... any idea why?

update.. well now i have a problem. I tried it the other way

rpm -Uvh --nodeps --force *.rpm

It seemed to update.. things registerred as 3.2 but

When I restarted, in runlevel 5, it didn't boot to the gui login.. and when i logged in and ran startx I received an error stating, XIO : fatal IO error 104 (connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.

When I run startkde the following comes up.

xsetroot : unable to open display ''
xset: unable to open display ""
ksplash: cannot connect to xserver
kdeinit : Aborting. $DISPLAY is not set
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
startkde: Running shutdown scripts
startkde one.

Any thought or do i have to reinstall.. the thought is when stuff like this breaks it's an opportuinity to learn.. so i would appreciate any insight.

Nearest I can figure, something is screwed with my display entry in the XFree86config file.. but it all looks ok to me.

Thanks for your help.

Thanks
-h

My best guess would be that the "Change Source of Installation" in Yast is not set up properly. That would explain why you can't view the correct updates or get them to install.

If Yast is pulling from the proper FTP directory in that mirror it will automatically update to 3.2 when you reveal the update icon by re-ticking the box next to the KDE Desktop Environment selection heading. When you tick the update icon do you see all the corresponding update icons appear next to the individual components listed on the adjacent detail window? If not then the installation source has not changed.

Check the path again. Do this as a test:
Create a new installation path just as before. But this time use the following information:

At the Server and Directory Window click or fill in the following:
Protocol: FTP
Server Name: mirror.mcs.anl.gov
Directory on Server: pub/suse/i386/9.0
Leave the other boxes empty. Click "OK".
Make sure that the status indicator line says "On".

Now go back to the Yast control center main menu and click "Install and Remove Software".
Click "Selections" from the Filter drop down menu.

You should now see additional headings like Network/Server, KDE Development, Kernel Development.
If not then the installation source has not been properly changed.

What to check the paths in your web browser for verification? You can copy/past these into your address window and access them directly:

ftp://mirror.mcs.anl.gov/pub/suse/i386/9.0
ftp://mirror.mcs.anl.gov/pub/suse/i3...0/yast-source/

Thanks, i'll give that a shot, i'm reinstalling right now.. i changed some hardware anyway.. so it isn't a big deal.

Thanks again for your help and time.

I don't like upgrading my kernel too much.

If the kernel is the heart of the operating system - would you like someone else to play with your heart?

If you download the rpms from a KDE mirror, and run the command

rpm -i *.rpm --nodeps --force2

It will install over the 3.1.4 without fail, you must reboot and all is well, don't know why your using the SuSE mirror service the files will be out of date

well i did the mirror update and it worked like a charm

I am a little hesitant to do the force update at this point as last time it wouldn't start x afterwards..

out of curiosity.. is there a kernel update rpm in the same manor?

thanks

That SuSE mirror is always updated so that you can continue to install the latest files.
There is a detailed listing of the updates on the SuSE website but I just use Yast to recognize them automatically.

In case you ever have need of alternate mirrors, here's where to find them:
Official SuSE International Mirrors

I've not seen anything yet regarding the kernel update rpm.
Continue to let Yast check that pub/suse/i386/9.0 path that I gave you.
Updated files for 9.0 are placed there as they become availiable.

Well everything went quite good. I downloaded the needed files and solved the dependencies but when I installed them and rebooted my machine I was back to the old KDE 3.14 again.

What happened there?

Using VMWare, and attempting various installs about 10-12 times, I figured out what I believe to be a recipe for success. It is kind of a combination of the two major suggestions here: first downloading the base components, and --nodep'ing the installation, then pointing YaST to a new installation source, and completing the install.

I wrote up an entire article and posted it on my site at perfectisolation.org

Thanks to every one who contributed to this!

Very nice! I really liked the detail on how to update! I am going to be installing Suse on my main computer here in a day or two and I need the new versions of umbrello and kdevelop so I'll try your method to update to kde 3.2! Thanks.

Hi,
Just one thourght on your tutorial the rpms from kdes' own ftp mirrors run the suseconfig tool, are the ones from SuSE not the same. The rpms from KDE have the simplest install I have ever seen even updating the window manager settings if they need changing.

/sbin/yast ?install *.rpm

haven't used this much but it's worth trying when installing rpmz

not sure if there is even a benefit over rpm -Uvh *.rpm

oobnuker I followed your guide on my desktop system and it worked great! The only things that needed to be changed was to not put the first '/' on the location like it says on your page. I simply entered the location as:

pub/suse/i386/supplementary/KDE/update_for_9.0/yast-source/

not

/pub/suse/i386/supplementary/KDE/update_for_9.0/yast-source/

After I upgraded kde I decided to add the other location and upgrade all the packages.

pup/suse/i386/9.0/

This allowed the instalation of all the newer packages out! The system is running perfectly and thanks to your guide I didn't lose any of the SuSE addons! I think it's amazing what happens when you get a bunch of people together working towards a single goal!

Hey - I fired up the ol' VMWare machine and tried this:

And it worked flawlessly - It appears like it performed exactly like:
It did not uninstall kdebase3-SuSE (a good thing) - so this would work perfectly well as an alternativc - thanks.

As far as the other comments go:

I'm glad it worked for and thanks for the feedback!

I'm not exactly sure if there is a difference between the rpm's from KDE and SuSE, but I like the way SuSE breaks them down into different folders on their ftp - that way, I can just download basically everything in the "base" folder, with a couple of additions - versus going through the entire folder from the KDE site, or, god forbid, downloading the whole folder - which contains a lot of crap that I don't need.