I am NOT a guru in the Linux world. I installed Suse 9.1 Pro a couple of months ago. A few weeks ago I tried (as I had successfully done before on numerous occasions) using yast2 to do an online update. After retrieving the required patches, yast2 starts the installation of the patches and just hangs/freezes while trying to install the first package. The progress bar just stalls at say 25% indefinitely until I kill the process. I have tried deselecting/selecting different patches and using different source servers, with the same result. Even tried yast in stead of yast2, same result.

I have a Toshiba laptop Sattelite 1955 S801
>uname -a
Linux my_box 2.6.5-7.108-default #1 Wed Aug 25 13:34:40 UTC 2004 i686 i686 i386 GNU/Linux

Anyboby knows how I can successfuly do online updates using yast(2)?

I'm currently using 9.1 as well and ran into a similar problem. I would start YOU and it would just sit there, staring at me with a blank face, never moving. What I found out one day while making a sandwich was...The YOU takes forever to actually do its thing.

The last time I ran this, I think it took about 10 or 15 minutes to finish. I'm not running the worlds fastest system, but it's a 2.6ghz with 1gig ram, a cable modem, and runs great on everything I do with it. However, YOU takes forever. I guess what Im getting at is, next time you try YOU, go make a sandwich and let it sit for a few minutes.

I'm not sure if that's the answer you were looking for, but thought it might help some folks new to YOU. If you don't get any results, you might be able to re-install YOU, although I'm not sure how much work that involves since I'm semi-new to Linux myself...

Do you get any messages in /home/<user>/.y2log or /var/log/YaST/y2log or /var/lib/YaST2/you/youlog ?

Does this happen at normal package installations (not updates) also? In that case it could be a corrupted rpm database. Try to repair it with rpm --rebuilddb (backup /var/lib/rpm before).

Is it always one package that freezes or does it happen with other packages, too? Maybe there is a corrupted download that causes the trouble. Unfortunatly I don't know where the rpm's are stored. You could also delete yast related data in /tmp. Just plain ideas, nothing that I have tried before...

maybe there is a patch for yast2, and maybe if you install it alone, it will work...then(maybe) that will fix the problem...just a guess