** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Triaged
** Summary changed:
- crypttab not generated in /etc/
+ Ubiquity does not support LUKS in manual partitioning mode
--
You received this bug notification be
I'm seeing this in the 18.04 Beta 1 installer also. If you use manual
partitioning and provide a /boot which is on LVM on LUKS, ubiquity does
not provision an /etc/crypttab and the resulting system is not bootable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Changed in: ubiquity (Ubuntu)
Status: Expired => New
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168115
Title:
crypttab
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168
installing on existing luks/btrfs doesn't ask for passphrase at boot
ubuntu 14.04.3 LTS, 15.04, 16.04
attached installation syslog and partman are from 16.04
after manual cryptsetup luksOpen as required to install on existing luks/btrfs
I selected the existing btrfs as root (having renamed the
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1168115/+attachment/4651419/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168115
Title:
crypt
** Attachment added: "partman"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1168115/+attachment/4651420/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168115
Title:
cry
Dear Phillip,
Thanks for your reply. I did all of that in my original bug report
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1492889 but that
has been marked as a duplicate of this one, which is why I posted here
with the 16.04 update.
Thanks.
--
You received this bug notification
There is not enough information here to understand or reproduce the
problem. Please provide a better description of what you did, what
errors you got, and attach the syslog and partman log files. They can
be found in /var/log while you are still running the installation, or
they are copied to the
bug still present as of 16.04
this bug has been present since at least 13.04
this bug prevents installation of a working system
why is it still Undecided and Unassigned?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Summary changed:
- crypttab not generated in /etc/ on raring ringtail 13.04
+ crypttab not generated in /etc/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168115
Title:
crypttab not generated
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168115
Title:
c
present in 14.04.3 and 15.04:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1492889
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168115
Title:
crypttab not generated in /etc/ on raring r
The cryptsetup package does include code to create a template
/etc/crypttab on first install, and I've confirmed in a raring chroot
that this still works correctly. If this is not happening for you, I
suspect this is related to ubiquity's support for luks installs
overriding and deleting the file
no i chrooted directly after installation, from live environment, and there was
no /etc/crypttab, even after reinstalling cryptsetup, I thought it might be
deprecated, and tried to boot without it - without success, then I thought,
info of the encrypted lvm now goes somewhere else, but couldn't
added further info
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168115
Title:
crypttab not generated in /etc/ on raring ringtai
so you chrooted into the target environment, edited /etc/crypttab, and
after reboot the file was not there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168115
Title:
crypttab not generated in /et
sorry,
yes it is encrypted, i just reformatted root and boot partitions, and kept home
partition.
from lucid to quantal it was always there after installing.
short description about my installprocedure: booting live-cd, cryptsetup
luksOpen, install, chroot, adding a few modules in /etc/modules,
I don't understand. Why are you expecting a crypttab to be created on
package install? You say you were installing into an existing lvm; you
don't say that this was an encrypted one. So what are you expecting to
find in /etc/crypttab at install time?
** Changed in: cryptsetup (Ubuntu)
St
19 matches
Mail list logo
