Martin,
Another interesting tidbit is that this pre-lightdm passphrase prompt
isn't actually doing anything... you can enter a blank passphrase or the
wrong passphrase, and it will still happily proceed to lightdm.
Here's the output you asked for:
$ systemctl --all | grep -i swap
dev-mapper-cryptswap1.device
loaded inactive dead start dev-mapper-cryptswap1.device
systemd-cryptsetup@cryptswap1.service
loaded activating start start Cryptography Setup for
cryptswap1
dev-disk-by\x2did-ata\x2dCrucial_CT120M500SSD3_14260C6F95F9\x2dpart3.swap
loaded active active
/dev/disk/by-id/ata-Crucial_CT120M500SSD3_14260C6F95F9-part3
dev-disk-by\x2did-wwn\x2d0x10806682451855888394x\x2dpart3.swap
loaded active active
/dev/disk/by-id/wwn-0x10806682451855888394x-part3
dev-disk-by\x2dpartlabel-primary.swap
loaded active active /dev/disk/by-partlabel/primary
dev-disk-by\x2dpartuuid-54ce1181\x2d8e2b\x2d456d\x2db679\x2d6a22d25fd361.swap
loaded active active
/dev/disk/by-partuuid/54ce1181-8e2b-456d-b679-6a22d25fd361
dev-disk-by\x2duuid-92a5e233\x2dc249\x2d42df\x2d8425\x2d3d6e8ac3af41.swap
loaded active active
/dev/disk/by-uuid/92a5e233-c249-42df-8425-3d6e8ac3af41
dev-mapper-cryptswap1.swap
loaded inactive dead start /dev/mapper/cryptswap1
dev-sda3.swap
loaded active active Swap Partition
swap.target
loaded inactive dead Swap
$ find /run/systemd/generator* | grep -i swap
/run/systemd/generator/dev-mapper-cryptswap1.device.d
/run/systemd/generator/dev-mapper-cryptswap1.device.d/90-device-timeout.conf
/run/systemd/generator/dev-mapper-cryptswap1.device.requires
/run/systemd/generator/dev-mapper-cryptswap1.device.requires/systemd-cryptsetup@cryptswap1.service
/run/systemd/generator/cryptsetup.target.requires/systemd-cryptsetup@cryptswap1.service
/run/systemd/generator/dev-disk-by\x2duuid-92a5e233\x2dc249\x2d42df\x2d8425\x2d3d6e8ac3af41.device.wants/systemd-cryptsetup@cryptswap1.service
/run/systemd/generator/systemd-cryptsetup@cryptswap1.service
/run/systemd/generator/swap.target.requires
/run/systemd/generator/swap.target.requires/dev-mapper-cryptswap1.swap
/run/systemd/generator/dev-mapper-cryptswap1.swap
/run/systemd/generator.late/swap.target.wants
/run/systemd/generator.late/swap.target.wants/dev-sda3.swap
/run/systemd/generator.late/dev-sda3.swap
--
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/1447282
Title:
Prompted for cryptoswap passphrase when using GPT partitioning +
encrypted home directory (ecryptfs)
Status in systemd package in Ubuntu:
New
Bug description:
I'm still sorting out the details and eliminating variables, but as
far as I can tell:
Steps to reproduce
===============
1) Install Ubuntu using GPT partitioning for the OS drive[*]
2) Choose "require my password to login", and check "encrypt my home
directory"
Expected behavior
===============
No special user interaction should be required to initialized the
crytposwap other than normally logging in
Actual behavior
============
Prior to lightdm coming up, you will be prompted to enter your
passphrase to unlock the cryptoswap, similar to how you would be
prompted to unlock the OS drive when using full disk encryption (see
attached photo).
When lightdm comes up, you have to enter your password/passphrase
again to login.
Work-arounds
===========
1) This only seems to happen when using GTP partitioning, not MBR...
so use MBR if you can
2) Even with GTP partitioning, booting with init=/sbin/upstart seems
to reliably fix the problem, so it certainly seems systemd related
Notes
=====
* As far as I can tell, there isn't a way to force Ubiquity to create
a GPT partition table when the OS drive is < 2TB, but it will
automatically use GPT partitioning when the OS drive is >= 2TB. My
particular test was done using the System76 imaging server, which by
default uses GPT partitioning even when the OS drive is < 2TB.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 22 11:40:29 2015
EcryptfsInUse: Yes
MachineType: System76, Inc. Kudu Professional
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic
root=UUID=e6c5aea5-d57c-410d-abce-66e96175e946 ro quiet splash vt.handoff=7
SourcePackage: systemd
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.03.03RS76
dmi.board.asset.tag: Tag 12345
dmi.board.name: Kudu Professional
dmi.board.vendor: System76, Inc.
dmi.board.version: kudp1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: kudp1
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnKuduProfessional:pvrkudp1:rvnSystem76,Inc.:rnKuduProfessional:rvrkudp1:cvnSystem76,Inc.:ct9:cvrkudp1:
dmi.product.name: Kudu Professional
dmi.product.version: kudp1
dmi.sys.vendor: System76, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447282/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
