Ewan Leith wrote:
i cant look it up right now, but im sure someone mailed the list with almost the exact same problem a couple (3?) of weeks ago, they did find a solution i think, but i cant remember what it was.
you might want to look in the archives.
I did, before resubscribing to the list to ask myself. I didn't find this particular problem. (Various people having problems during initial install, people experiencing system-wide crashes, which this is not, and the GPG problem which I don't seem to encounter either. Someone having a hang during partitioning (which went flawlessly here). One guy had a problem with Yast2 hanging until he removed his network card - which is not an option, this is a headless server.) ... oh, that's interesting. Someone had a completely unrelated error which they resolved with rm -rf /tmp/YaST* and I thought I'd try that on the offchance and that seems to have done the trick here as well. -- Rachel
Ewan
On Sun, 2002-06-09 at 17:00, Rachel Greenham wrote:
On an already-installed system, when I try to install additional packages or run an online update, Yast2 hangs at the point just before it opens the window where the RPMs are installed.
This happens whether the installation medium is Network (NFS) or Hard disk (don't get me started! It won't hold the hard disk directory configuration either). The machine doesn't have a CD or DVD drive, but contains the DVD iso image which is mounted using loopback mount and shares it as NFS to the rest of the network.
It happens whether I use the ncurses or qt user interface.
rpm at the command-line works OK.
When it hangs, the "y2base" process is sitting there taking up all available processor time, but not growing in memory beyond about 20Mb.
If I *reboot* the box, I can then install stuff in Yast2 *once*. On a subsequent attempt it fails.
I'm about to install the FTP-version's Yast2, when it finishes downloading, to see if it makes a difference as is, and then to see if using an FTP installation medium also makes a difference.
The oddest thing is, this is now the sixth SuSE 8.0 install I've done (on different machines), and the first time this problem has turned up. I've also found no reference to anyone else having this problem. The only significant difference I can think of is that with this machine I started with a "Minimal" install and have been building it up. Something is presumably not being installed that's needed by something that doesn't complain at its absence but just goes wrong. At this rate it'll be worth registering my copy and getting SuSE installation support going. :-)
-- Rachel
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com