touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Thanks Jason. Just to make sure my suspicion is correct, can you please
give me the output of "systemctl --all|grep swap" and give me all files
that turn up in "find /run/systemd/generator* | grep swap"?

I figure the

Apr 22 11:34:38 jason-Kudu-Professional kernel: Adding 4194300k swap on
/dev/sda3. Priority:-1 extents:1 across:4194300k SSFS

comes from systemd-gpt-generator that picks up the raw/bogus /dev/sda3
partition, and as it's slightly faster it's causing this:

Apr 22 11:38:31 username-Kudu-Professional systemd-cryptsetup[645]:
Loading of cryptographic parameters failed: Invalid argument

which makes cryptsetup fail.

FTR, GPT will be used (by default) if you install on an EFI system.

-- 
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