Ensure minimum total memory available to desktop systems

This bug was fixed in the package ubiquity - 22.10.5

---------------
ubiquity (22.10.5) kinetic; urgency=medium

  [ Michał Sawicz ]
  * Run after cloud-init if installed

  [ Dimitri John Ledkov ]
  * Ensure minimum available amount of memory available (LP: #1979997)

 -- Dimitri John Ledkov <email address hidden> Wed, 13 Jul 2022 14:19:20 +0100

Hello Dimitri, or anyone else affected,

Accepted ubiquity into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/22.04.17 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

My test procedure: The the new ubiquity version in QEMU on amd64.

1. Boot ubuntu-22.04-desktop-amd64.iso
2. Select "Try Ubuntu"
3. Open terminal and run:
```
xrandr -s 1920x1080
echo "deb http://archive.ubuntu.com/ubuntu/ jammy-proposed main" | sudo tee /etc/apt/sources.list
sudo apt update
sudo apt install ubiquity-frontend-gtk=22.04.17 ubiquity-ubuntu-artwork=22.04.17 ubiquity=22.04.17
```
4. Start ubiquity and install Ubuntu
5. After reboot check SWAP
```
grep SwapTotal /proc/meminfo
```

Results:

| Type | Memory | SWAP | disk size | Diff |
| unencrypted | 10240 MiB | 2097148 kB | 26.844 GB | 0 |
| unencrypted | 8192 MiB | 2097148 kB | 26.844 GB | 0 |
| unencrypted | 5120 MiB | 2744316 kB | 26.844 GB | |
| unencrypted | 5120 MiB | 2891772 kB | 80.531 GB | -0.24 GiB |
| unencrypted | 2048 MiB | 2744316 kB | 26.844 GB | |
| unencrypted | 2048 MiB | 6191100 kB | 80.531 GB | -0.10 GiB |
| encrypted LUKS | 10240 MiB | 1998844 kB | 107.37 GB | -0.09 GiB |
| encrypted LUKS | 8192 MiB | 1998844 kB | 107.37 GB | -0.09 GiB |
| encrypted LUKS | 5120 MiB | 2756604 kB | 107.37 GB | -0.37 GiB |
| encrypted LUKS | 2048 MiB | 5902332 kB | 107.37 GB | -0.37 GiB |
| zfs | 10240 MiB | 2097148 kB | 107.37 GB | 0 |
| zfs | 8192 MiB | 2097148 kB | 107.37 GB | 0 |
| zfs | 5120 MiB | 2891772 kB | 107.37 GB | -0.24 GiB |
| zfs | 2048 MiB | 6191100 kB | 107.37 GB | -0.10 GiB |
| zfs encrypted | 10240 MiB | 2097148 kB | 107.37 GB | 0 |
| zfs encrypted | 8192 MiB | 2097148 kB | 107.37 GB | 0 |
| zfs encrypted | 5120 MiB | 2891772 kB | 107.37 GB | -0.24 GiB |
| zfs encrypted | 2560 MiB | 5640188 kB | 107.37 GB | -0.12 GiB |

Note:

1. This tests needs to be done with a disk size of >= 60 GB to avoid hitting the 10% of disk space limit.
2. The installation with zfs encrypted with 2 GiB was OOM killed every time (tried multiple times). So I used 2.5 GiB instead.

Result after running the complete test matrix: The resulting SWAP size is identical to the expected SWAP size or up to 12 % below the expected size.

I consider this outcome is successful verification.

This bug was fixed in the package ubiquity - 22.04.17

---------------
ubiquity (22.04.17) jammy; urgency=medium

  [ Dimitri John Ledkov ]
  * Ensure minimum available amount of memory available (LP: #1979997)

 -- Steve Langasek <email address hidden> Fri, 15 Jul 2022 17:02:02 -0700

The verification of the Stable Release Update for ubiquity has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.