[Bug 1594035] Re: unable to shut down the system after suspend / resume
** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594035 Title: unable to shut down the system after suspend / resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594035] Re: unable to shut down the system after suspend / resume
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 attempted reboot. Disabling cryptswap worked
around the problem. The hang-on-startup problem initially appeared to
be centered on hit-and-miss automatic key generation for ecryptfs; but
the unattended-upgrades problem is simultaneous. Don't yet know if I've
this Bug (viz., #1594035) in specific, or have to file a new Bug, as of
6 December 2016; the answer depends on replies to Question #404663,
opened 5 December.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594035
Title:
unable to shut down the system after suspend / resume
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594035/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594035] Re: unable to shut down the system after suspend / resume
** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594035 Title: unable to shut down the system after suspend / resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594035] Re: unable to shut down the system after suspend / resume
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594035 Title: unable to shut down the system after suspend / resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594035] Re: unable to shut down the system after suspend / resume
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 device show by "헰헮혁 /proc/swaps", or /dev/mapper/cryptswap1." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594035 Title: unable to shut down the system after suspend / resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594035] Re: unable to shut down the system after suspend / resume
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" shows not LUKS partition. 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.
Looking at /var/log/syslog, I see that cryptsetup failed because
/dev/urandom is not available. ("grep crypt /var/log/syslog" for
details.)
Further, I notice that poweroff.target is disabled. When I enable it
(systemctl enable poweroff.target), shutdown works as expected unless
the computer has resumed from suspend.
The work around suggested by Mr. Pellegrino works, but of course that
means that swap is not encrypted, which is of course a security
vulnerability.
Here is my working theory: On boot-up, systemd tries to create an
encrypted swap, but when it cannot, systemd creates an unencrypted swap.
(Feature or bug? There would be competing considerations, so it is hard
to say.) After resume from suspend, which of course involves (on
suspend) writing RAM to swap and then (on resume) reading from swap to
RAM, the system thinks there should be an encrypted swap (because that's
what /etc/fstab and /etc/crypttab say), but can't find it and gets
confused when time comes to shutdown.
This being a security issue, it should be given attention.
** Changed in: systemd (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/1594035
Title:
unable to shut down the system after suspend / resume
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594035/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594035] Re: unable to shut down the system after suspend / resume
Bug #1447282 may be relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594035 Title: unable to shut down the system after suspend / resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594035] Re: unable to shut down the system after suspend / resume
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 --- > cryptswap1 UUID=d1bd47b1-9969-4cf6-bb7e-482a50b41ffa /dev/urandom > swap,offset=1024,cipher=aes-xts-plain64 I also set /etc/fstab to use the swap partition directly rather than /dev/mapper/cryptswap1: $ diff /etc/fstab /etc/fstab~ 16,17c16,17 < UUID=d1bd47b1-9969-4cf6-bb7e-482a50b41ffa none swap sw 0 0 < #/dev/mapper/cryptswap1 none swap sw 0 0 --- > #UUID=d1bd47b1-9969-4cf6-bb7e-482a50b41ffa none swap sw 0 0 > /dev/mapper/cryptswap1 none swap sw 0 0 On this machine, it seems encrypted swap was not working anyway as per lines in the attached JournalErrors.txt: Jun 18 17:56:14 username-Lemur systemd-cryptsetup[446]: Failed to activate with key file '/dev/urandom': Device or resource busy ... Jun 18 17:56:18 username-Lemur systemd-cryptsetup[446]: Loading of cryptographic parameters failed: Invalid argument Jun 18 17:56:18 username-Lemur systemd-cryptsetup[446]: Failed to activate: Invalid argument Jun 18 17:56:18 username-Lemur systemd[1]: Failed to start Cryptography Setup for cryptswap1. Jun 18 17:56:18 username-Lemur systemd[1]: Dependency failed for Encrypted Volumes. Jun 18 17:56:18 username-Lemur systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. Jun 18 17:56:18 username-Lemur systemd[1]: Dependency failed for /dev/mapper/cryptswap1. Jun 18 17:56:18 username-Lemur systemd[1]: Dependency failed for Swap. Jun 18 17:56:18 username-Lemur systemd[1]: systemd-cryptsetup@cryptswap1.service: Failed with result 'exit-code'. Jun 18 17:56:18 username-Lemur systemd-cryptsetup[805]: Failed to activate with key file '/dev/urandom': Device or resource busy With encrypted swap disabled as per the changes to /etc/crypttab and /etc/fstab, the machine now shuts down as expected even when suspend/resume cycles occur during the user session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594035 Title: unable to shut down the system after suspend / resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
