Hi, I had the same problem when running a backup job manually. When I had my backup configured to run automatically, I did not (literally) observe this type of behavior, as the session didn’t run in a terminal window or through the GUI. In any event the XML auto installation file didn’t get written when the job was automated. Here’s an odd thing. Try creating a system backup profile, save it, and then try deleting it. If me guess is correct, you’ll still see the profile the next time you launch Yast > System backup. I have also seen this problem on a friend’s computer, also SuSE Pro 9.1. Good luck with this problem, Rocky Pope torkildr@tihlde.org (Torkild Ulvøy Resheim), 6/3/04, +0200, 4:32 PM
My YaST2 backup hangs on "Write autoinstallation profile", it does not use CPU but can go on for hours if I don't kill it. I can't find anything in the logs that might be related. Any ideas?