** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1594035
Title:
unable to shut down the system after su
I have a similar issue with ubuntuยฎ 16.04.1: My own system recently
hung attempting to initialize not more than two of five swap partitions
("[<>] A start job is running for dev-mapper-cryptswap?.device
(??m??s / No limit)") on several attempts and subsequently hung on
unattended-upgrades on a
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
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/1594035
Title:
unable to shut down the system after suspe
As noted by @loyeyoung, a better work-around than the one in Comment #2
may be to disable swap rather than running with an encrypted home
directory and unencrypted swap as that state is a security liability.
For the case where hibernate depends on swap, hibernate would also need
to be disabled.
--
Correcting error:
"This is so no matter which path to the swap partition I use, including:
/dev/disks/by-uuid/, the device show by "grep /proc/swaps", or
/dev/mapper/cryptswap1."
๐ฆ๐ต๐ผ๐๐น๐ฑ ๐๐ฎ๐:
"This is so no matter which path to the swap partition I use, including:
/dev/disks/by-uuid/, the
Being a fellow pilgrim in the Way of the Penguin, I can confirm the
exact same facts as Mr. Pellegrino on clean install of Ubuntu Mate
16.04.
It appears that the swap partition is not actually encrypted at all.
Syslog shows that encryption failed, and "cryptsetup -v isLuks
/path/to/partition" show
Bug #1447282 may be relevant.
--
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/1594035
Title:
unable to shut down the system after suspend / resume
Status in systemd packag
I confirmed that disabling encrypted swap is a work-around for the
inability to shut down. I commented out the cryptswap1 entry from
/etc/crypttab:
$ diff /etc/crypttab /etc/crypttab~
1c1
< # cryptswap1 UUID=d1bd47b1-9969-4cf6-bb7e-482a50b41ffa /dev/urandom
swap,offset=1024,cipher=aes-xts-plain64
8 matches
Mail list logo
