Bug 8361 - GNOME install does not figure out minimums til too late
Summary: GNOME install does not figure out minimums til too late
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-01-11 01:43 UTC by Stephen John Smoogen
Modified: 2015-01-07 23:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-02-04 13:05:33 UTC
Embargoed:


Attachments (Terms of Use)

Description Stephen John Smoogen 2000-01-11 01:43:23 UTC
Ok I have a 800 meg SCSI cdrom and selected GNOME workstation install. The
install partitions the disk and then tells me when I finally get to
installing packages that / is too small.

Hitting OK causes a Python exception

File "/usr/bin/anaconda", line
336 in ?
 intf.run(todo, test=test)

File "/usr/lib/anaconda/text.py"
line 1078 in run
 rc= apply(step[1](),step[2])

File "/usr/lib/anaconda/text.py"
line 623, in __call__
  if todo.doInstall ():

File "/usr/lib/anaconda/todo.py"
line 1288, in doInstall
   self.fstab.umountFilesystems()
TypeError: not enough arguments;
expected 2, got 1

Comment 1 Hans de Goede 2000-01-14 15:11:59 UTC
This are really 2 problems:
-it warns that there's not enough space after formatting which makes reproducing
 it sorta painfully.
-it shouldn't crash after this message but take you back to the package
 selection or the install type selection.

I also have seen this bug I think it happens on any config where you don't have
enough diskspace. But here's how I can reproduce it:
-do pcmcia install on 486dx75 / 12mb ram / 360mb hd laptop
-choose nfs install
-choose custom
-select to much
-wait for to much dialog (which is after format !!!)
-press enter
-the above trace appears, it's identical on my machine

Comment 2 Jay Turner 2000-02-04 13:05:59 UTC
Installer does not partition the disk until after this space check, so something
else might be going on here.  The only thing that the installer will do before
this space check is activate swap space if you are running a low memory machine
(I think that the threshold is at 32M for Intel)

As for the python exception after clicking "OK", this is fixed in beta3.


Note You need to log in before you can comment on or make changes to this bug.