Public bug reported:

Using the amd64 iso from
http://cdimage.ubuntu.com/xubuntu/releases/18.04/beta-1/

Possibly unrelated but addition infos:
- Selecting 'Deutsch' as the language before booting the installer
- Selecting 'Expert' in the Options before booting
- Connecting to a Wifi during installation (Sidenote: Once I select the wifi in 
the installer and enter the password in NetworkManager, there is *no* feedback 
whatsoever if the connection succeeded. I just click 'Next' blindly. It would 
be nice to have some feedback of the connection state there.)

The actual issue:
- When choosing the installation location I choose 'something different' to 
manually edit partitions.
- Create a new partition table
- Create a crypt device in the free space
- Click on 'Reset'

-> First bug: the crypt device /dev/mapper/sda1_crypt is not reset and
stays configured. Going back and into the manual settings again does not
help.

- Remove the crypt partition from sda
- Create a new normal partition at the beginning of the disk (e.g. 200mb ext4 
for /boot)
- Create a crypt device on the remaining free space

-> Messagebox appears that says creation of the crypt device failed.
Clicking it away makes it re-appear. Even if the first bug was fixed and
crypt devices can be cleanly removed/rest, failing to create the crypt
device should only show one message box and return to a usable state and
not get into a warning loop. (which might be triggered by some other
bug)

Verified on VBox and actual hardware.

** Affects: ubiquity (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758310

Title:
  Messagebox-look when manually configuring partitions with luks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1758310/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to