![](https://seccdn.libravatar.org/avatar/2b1eb030e03bd91bb4f8e20da0671232.jpg?s=120&d=mm&r=g)
Hi, Geoffrey, I feel the same frustration. Instead of commenting your issues one by one, I'll just tell you how I did with the 3 machines I've installed up to now. During initial installation "Online Update Configuration" adds a patch repository and I run YOU several times. Invariably, after installing new packages, YOU stops working the same way as in your case: the window just goes away. From that point on I use Zen Online Updater, which is the icon on the taskbar. Since I am logged in as root during installation, I just click on the icon and install the updates. Then I set up automatic updates overnight with Yast2/Software/Online Update Setup. When I notice that the taskbar icon still shows patches were not installed, it means that they may require reboot (such as a kernel patch), because I left the option "Skip interactive patches" checked. So, I run "rug up -t patch" as root in the command line and accept licenses, reboot if needed, and my system is up-to-date. (Stupidly it does not allow you do add a privileged user to run the Zen Updater by just clicking th icon. You would have to do that with "rug add-user" in the command line.) From time to time I check if my patch repository is still OK (active), by running "rug sl", because the Online Updater just tells you "no software updates available", which may mean that your system is up-to-date, or that it cannot reach the repository. If I find that my server is inactive, I delete this source from Yast2/Software/Installation Source and run yast2/Software/Online Update Configuration again, which adds a new working repository. All these are known bugs that Suse is working on (see Bugzilla: https://bugzilla.novell.com/index.cgi ), and they hopefully will be fixed soon. Obviously this is not as smooth a ride, as we have have become accustommed to with Suse, but it has kept me going, while I wait for the Suse guys to fix the updating process. They already updated libzypp in the past days, and I hope zmd is also fixed soon. I have another 10 machines running 9.3 that I want to upgrade (I always do fresh install of the root partition), but I will hold off until the online update issue is solved. I've used Suse since 7.1 myself and I want to give them a chance to fix the mess created by this transition of update methods. Once it's sorted out, they are promising a new 10.1 ISO that contains all the patches that make it work, as we got used to: http://lists.suse.com/archive/suse-linux-e/2006-Sep/0887.html I am eagerly waiting for that. Carlos FL On Saturday 23 September 2006 10:51, Geoffrey wrote:
I've spent hours trying to resolve this issue. I've searched for a solution, found a couple, none appear to work. Received suggestions and recommendations from a very active person at @suse.de, still no luck.
On a new install of SuSE 10.1, we all know there are problems with online update.
[...]
I'm at my wits end on this one. I've been using SuSE since 6.4 and rely on it as my primary Linux solution. I've got a number of clients running SuSE, but if I can't get this update to work on this box, I'll be looking for another distro.
This is the most frustrating problem I've dealt with. I've re-installed on this same box 6 times, trying to get this to work. I can't upgrade any of my other boxes or my clients until I've resolved this issue.