| 2022-03-14 14:48:27 |
Hannes Hegewald |
bug |
|
|
added bug |
| 2022-03-14 14:56:57 |
Erich Eickmeyer |
ubiquity (Ubuntu): status |
New |
Incomplete |
|
| 2022-03-14 15:16:13 |
Hannes Hegewald |
tags |
encryption zfs |
apport-collected encryption jammy ubiquity-22.04.7 ubuntu zfs |
|
| 2022-03-14 15:16:14 |
Hannes Hegewald |
description |
Issue: As soon as security keys for an encrypted ZFS setup are entered, the system will get encrypted, even if this is not desired anymore and has been deselected in the installation process prior to proceeding with the installation.
Desired behavior: I expect that I can decide against encrypting my system, even when I have entered and not submitted security keys beforehand.
What happened: During the installation process, I first decided to go for an encrypted ZFS partition layout. Thus, I chose 'Advanced features', checked, 'Erase disk and use ZFS', as well as 'Encrypt the new Ubuntu installation for security', and clicked OK. I then clicked 'Continue' and entered two matching security keys. I did not opted for a recovery.
At this very point I changed my mind about encrypting the file system. I just clicked 'Back' without clearing my previously entered security keys. In 'Advanced features' I deselected the 'Encryption' checkbox and clicked 'Continue'. I was then asked to confirm the partition layout, which I did.
The rest of the installation went normal. As a surprise to me, I was asked for the security key I had previously entered. The system then boots normal.
Installation media: jammy-desktop-amd64.iso, downloaded March 11. Tested in VirtualBox and QEMU. |
Issue: As soon as security keys for an encrypted ZFS setup are entered, the system will get encrypted, even if this is not desired anymore and has been deselected in the installation process prior to proceeding with the installation.
Desired behavior: I expect that I can decide against encrypting my system, even when I have entered and not submitted security keys beforehand.
What happened: During the installation process, I first decided to go for an encrypted ZFS partition layout. Thus, I chose 'Advanced features', checked, 'Erase disk and use ZFS', as well as 'Encrypt the new Ubuntu installation for security', and clicked OK. I then clicked 'Continue' and entered two matching security keys. I did not opted for a recovery.
At this very point I changed my mind about encrypting the file system. I just clicked 'Back' without clearing my previously entered security keys. In 'Advanced features' I deselected the 'Encryption' checkbox and clicked 'Continue'. I was then asked to confirm the partition layout, which I did.
The rest of the installation went normal. As a surprise to me, I was asked for the security key I had previously entered. The system then boots normal.
Installation media: jammy-desktop-amd64.iso, downloaded March 11. Tested in VirtualBox and QEMU.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: ubiquity 22.04.7 [modified: lib/partman/automatically_partition/question]
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Tags: jammy ubiquity-22.04.7 ubuntu
Uname: Linux 5.15.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
|
| 2022-03-14 15:16:15 |
Hannes Hegewald |
attachment added |
|
Casper.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568677/+files/Casper.txt |
|
| 2022-03-14 15:16:16 |
Hannes Hegewald |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568678/+files/Dependencies.txt |
|
| 2022-03-14 15:16:17 |
Hannes Hegewald |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568679/+files/ProcCpuinfoMinimal.txt |
|
| 2022-03-14 15:16:18 |
Hannes Hegewald |
attachment added |
|
UbiquityDebug.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568680/+files/UbiquityDebug.txt |
|
| 2022-03-14 15:16:20 |
Hannes Hegewald |
attachment added |
|
UbiquityDm.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568681/+files/UbiquityDm.txt |
|
| 2022-03-14 15:16:21 |
Hannes Hegewald |
attachment added |
|
UbiquityPartman.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568682/+files/UbiquityPartman.txt |
|
| 2022-03-14 15:16:23 |
Hannes Hegewald |
attachment added |
|
UbiquitySyslog.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568683/+files/UbiquitySyslog.txt |
|
| 2022-03-14 15:21:59 |
Hannes Hegewald |
description |
Issue: As soon as security keys for an encrypted ZFS setup are entered, the system will get encrypted, even if this is not desired anymore and has been deselected in the installation process prior to proceeding with the installation.
Desired behavior: I expect that I can decide against encrypting my system, even when I have entered and not submitted security keys beforehand.
What happened: During the installation process, I first decided to go for an encrypted ZFS partition layout. Thus, I chose 'Advanced features', checked, 'Erase disk and use ZFS', as well as 'Encrypt the new Ubuntu installation for security', and clicked OK. I then clicked 'Continue' and entered two matching security keys. I did not opted for a recovery.
At this very point I changed my mind about encrypting the file system. I just clicked 'Back' without clearing my previously entered security keys. In 'Advanced features' I deselected the 'Encryption' checkbox and clicked 'Continue'. I was then asked to confirm the partition layout, which I did.
The rest of the installation went normal. As a surprise to me, I was asked for the security key I had previously entered. The system then boots normal.
Installation media: jammy-desktop-amd64.iso, downloaded March 11. Tested in VirtualBox and QEMU.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: ubiquity 22.04.7 [modified: lib/partman/automatically_partition/question]
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Tags: jammy ubiquity-22.04.7 ubuntu
Uname: Linux 5.15.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
Issue: As soon as security keys for an encrypted ZFS setup are entered, the system will get encrypted, even if this is not desired anymore and has been deselected in the installation process prior to proceeding with the installation.
Desired behavior: I expect that I can decide against encrypting my system, even when I have entered and not submitted security keys beforehand.
What happened: During the installation process, I first decided to go for an encrypted ZFS partition layout. Thus, I chose 'Advanced features', checked, 'Erase disk and use ZFS', as well as 'Encrypt the new Ubuntu installation for security', and clicked OK. I then clicked 'Continue' and entered two matching security keys. I did not opted for a recovery.
At this very point I changed my mind about encrypting the file system. I just clicked 'Back' without clearing my previously entered security keys. In 'Advanced features' I deselected the 'Encryption' checkbox and clicked 'Continue'. I was then asked to confirm the partition layout, which I did.
The rest of the installation went normal. As a surprise to me, I was asked for the security key I had previously entered. The system then boots normal.
Installation media: jammy-desktop-amd64.iso, downloaded March 11. Tested in VirtualBox and QEMU.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: ubiquity 22.04.7 [modified: lib/partman/automatically_partition/question]
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Tags: jammy ubiquity-22.04.7 ubuntu
Uname: Linux 5.15.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: ubiquity 22.04.7
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
RebootRequiredPkgs: Error: path contained symlinks.
Tags: jammy ubiquity-22.04.7 ubuntu
Uname: Linux 5.15.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
|
| 2022-03-14 15:22:00 |
Hannes Hegewald |
attachment added |
|
Casper.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568684/+files/Casper.txt |
|
| 2022-03-14 15:22:01 |
Hannes Hegewald |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568685/+files/Dependencies.txt |
|
| 2022-03-14 15:22:02 |
Hannes Hegewald |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568686/+files/ProcCpuinfoMinimal.txt |
|
| 2022-03-14 15:22:03 |
Hannes Hegewald |
attachment added |
|
UbiquityDebug.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568687/+files/UbiquityDebug.txt |
|
| 2022-03-14 15:22:04 |
Hannes Hegewald |
attachment added |
|
UbiquityDm.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568688/+files/UbiquityDm.txt |
|
| 2022-03-14 15:22:05 |
Hannes Hegewald |
attachment added |
|
UbiquityPartman.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568689/+files/UbiquityPartman.txt |
|
| 2022-03-14 15:22:07 |
Hannes Hegewald |
attachment added |
|
UbiquitySyslog.txt https://bugs.launchpad.net/bugs/1964788/+attachment/5568690/+files/UbiquitySyslog.txt |
|
| 2022-03-14 16:17:52 |
Erich Eickmeyer |
ubiquity (Ubuntu): status |
Incomplete |
New |
|
