Zesty & yakkety are both outdated and un-maintained since a while.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1668906
Title:
systemd occasionally hangs forever while boo
All passwords are already entered, the problem occurs some time after
the passwords have been entered, and as far as I could see on the debug
console, all encrypted devices exist under /dev/mapper, so it does not
seem to be caused by encryption (except for the fact that encryption
generataes long d
See the same issue on non encryted EXT4 ZZ partition.
That makes me thinking about, either:
- the previous shutdown was not fully clean: there is no orphaned nodes, but
these multi services elapsing timers
- some kind of races introduced a week or two back.
** Tags added: zesty
--
You receive
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 Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
Do you see a prompt to enter encrypted password?
Have you tried to blindly type the encrypted device password and hit enter to
continue booting?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.
6 matches
Mail list logo
