[Bug 1874066] Re: Cannot install on non-RST drive if RST is enabled and there is a second RST-enabled drive
Emil Lenngren
1874066 at bugs.launchpad.net
Fri Apr 23 22:34:03 UTC 2021
I also got hit by this bug when trying to install Ubuntu 21.04. I want
to install Ubuntu on a separate USB memory I have plugged into my
computer, but couldn't get past this step.
Thankfully ubiquity is written in Python so I could easily in my Live
session go to /usr/lib/ubiquity/plugins/ubi-prepare.py, remove the code
in the should_show_rst_page() method and change it to return the
constant False.
But I'd like to see an option "Continue and install on another disk" if
it is detected that another disk is plugged in that is usable.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1874066
Title:
Cannot install on non-RST drive if RST is enabled and there is a
second RST-enabled drive
Status in OEM Priority Project:
New
Status in ubiquity package in Ubuntu:
New
Status in ubiquity source package in Focal:
New
Bug description:
Test Case:
1. On a machine with 2 disk 1 spinning disk and 1 nvme disk, enable RST
2. Start ubiquity and proceed zith the installation to the partitioning step
Expected result
Despite RST being enabled, user should be able to install on the non-RST disk
Actual result
Installation is blocked on the RST page and user cannot proceed without disabling RST
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.14
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 21 12:35:53 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash nomodeset ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1874066/+subscriptions
More information about the foundations-bugs
mailing list