Andy, You may have hit on the solution for this problem. I know I had told Art that I had no problems after updating, but could not tell him what I did different that kept me working ok. With your findings, I am starting to see a pattern and possible solution too. When I download my patches via Yast2 Online update, I never keep the the files around, I always tell Yast2 to delete the files after update! Now, since you have moved yours, thus deleting them, suddenly everything begins to work again for you. Don't really see how this should affect Yast2, but it is looking like there is some hook there that does. Maybe someone else here could explain that relationship. Anyway, hope it works for others as well. The simple solutions are the most difficult sometimes. Patrick ------------------------ On Saturday 08 June 2002 22:24, Andy Stewart wrote:
Hi everybody,
I did something on my system that seems to have fixed the KDE 3.0.1 problem which broke YaST2. Perhaps this will work for you.
I went into the /var/lib/YaST/patches/i386/update/8.0/patches directory and moved all of the files therein to /tmp/foobar (an arbitrary temporary directory).
I then logged into KDE 3.0.1 as a non-root user. In a terminal window, I did "su - root" and once logged in as root, I started up yast2 with /sbin/yast2 and of course the YaST Control Center window appeared. I clicked Online Update and it worked(!). This was all in graphical mode (not ncurses). I successfully performed online updates again! This is the first time this has worked since upgrading to KDE 3.0.1.
By moving those files out of the patches directory (above), I had lost the information regarding which patches I had already installed. However, I let YaST reapply the patches and all went well.
I then started the KDE Control Center and clicked on: YaST2 modules Software Online Update Administrator Mode
I typed in my root password when prompted. The YaST online update window then properly appeared within the KDE Control Center window just as it should. I proceeded to do an online update from there (which of course was unnecessary since I had just done it, but I wanted to insure that the process was working).
I discovered that when I originally had reversed the order of the above steps, I encountered the "gpg error". That error condition no longer occurs.
Standard disclaimers apply - your mileage may vary, but hopefully this will work for you as well. If this process causes you grief, one could replace the files from the patches directory and (I suppose) one would be back to where they started.
I hope this helps,
Andy =========================== -- --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb