*** This bug is a duplicate of bug 1432265 ***
https://bugs.launchpad.net/bugs/1432265
Unfortunately this is pretty easy to reproduce. I installed Ubuntu
Server 15.10, set up an additional partition and formatted it with LUKS,
and added to crypttab. That is all it takes to make the boot
*** This bug is a duplicate of bug 1432265 ***
https://bugs.launchpad.net/bugs/1432265
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1432265 ***
https://bugs.launchpad.net/bugs/1432265
** This bug has been marked a duplicate of bug 1432265
does not ask for LUKS passphrases without plymouth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm the exact same behavior: if /etc/crypttab has entries for
non-root devices, then the only way to unlock with a password is to
force plymouth to run with the "splash" boot option.
I've been trying to test luks-encrypted data volumes (non-root) on
ubuntu-server and have hit this
I tried another test in an attempt to get /bin/systemd-tty-ask-password-
agent to prompt for a password. I ensured no other systemd password
agents were running (ps auxww | grep ask), then launched 'sudo /bin
/systemd-tty-ask-password-agent --watch --console' in one terminal and
launched 'sudo
I just noticed that I can enter the password and unlock the disk if I
boot with splash / plymouth enabled.
I normally do not use the "splash" boot option to boot up in text mode,
and the cryptsetup unit file or something does not seem to be able to
cope with that and does not query for the
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453912
Title:
systemd does not unlock dm-crypt password
To manage
Unfortunately, this bug is still current - I submitted all requested
information, there has been no activity in response, but the problem
still persists.
** Changed in: systemd (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Don't think i can verify this on the other computer as stated. It seems
to be a different problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453912
Title:
systemd does not unlock dm-crypt
BTW, is there anything else needed from my side or anything else I
should or can do to provide any required information?
I'm still having this issue and I fear my system might be rendered
unusable if the next Kubuntu update possibly removes upstart support
completely and with it the fallback boot
@Martin,
Sorry for late reply. I spilled juice in my computer and it fried. Never
gets old :-) I have a new computer so I cant do proper debugging
anymore. I will check a friends computer since I think he has the exact
same problem. On Wednesday next week that is (is in transit until then).
HTH
** Attachment added: The requested generator.tar file.
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4422419/+files/generator.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Indeed, the log doesn't even show an attempt to unlock cryptstore. In
that debug shell, can you please do
tar cf /root/generator.tar /run/systemd/generator*
and attach /root/generator.tar here?
** Summary changed:
- systemd does not allow to boot with /home on dm-crypt
+ systemd does not
14 matches
Mail list logo
