[Bug 1308530] Re: Cannot login after an upgrade from Saucy to Trusty with Ubiquity and encrypted home directory

[CSRedRat]

When this fixed in 14.04 Trusty Tahr for 14.04.1 (24 July)?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1308530

Title:
  Cannot login after an upgrade from Saucy to Trusty with Ubiquity and
  encrypted home directory

Status in Release Notes for Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Triaged

Bug description:
  Trusty Desktop amd64 20140415

  TEST CASE:
  1. Install Saucy Desktop with encrypted home
  2. Boot a Trusty ISO
  3. Select upgrade to Trusty
  4. Enter the same username and another password

  EXPECTED RESULT:
  User can log in

  ACTUAL RESULT
  User cannot login.
  If I boot to recovery mode and "sudo -i -u ubuntu" I get
  """
  $ sudo -i -u ubuntu
  open: No such file or directory
  Error locking counter
  """

  If I unlock the home directory with ecryptfs-mount-private I get:
  """
  $ ecryptfs-mount-private
  Enter your login passphrase:
  Inserted auth tok sig [XXXXXXX] into the user session keyring
  open: No such file or directory
  Error locking counter
  """

  But the home directory is not unlocked and mounted

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Wed Apr 16 14:59:42 2014
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  InstallationDate: Installed on 2014-04-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140415)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1308530/+subscriptions