home ecryptfs directory not accessible in X on boot

Bug #1324698 reported by Dash on 2014-05-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ecryptfs-utils (Ubuntu)
Undecided
Unassigned

Bug Description

Upgrade a notebook with SSD disk and /home/<user> directory in ecryptfs, from 12.04 to 14.04. After installation, on each reboot, the ecryptfs <user> partition is encrypted mounted when checking in console mode (tty[1,2,...,6] but *not* when entering users credentials in X greeting window. If, before entering those credentials, we open a tty console and run "sudo service lightdm restart" and switch back to X greeting windows, all is good.

In the case of login without restarting lightdm, behaviors are:

- ls -al shows cached directories created from time of login
- ls shows a README.TXT symbolic link to /usr/share/ecryptfs-utils/ecryptfs-mount-private.txt
- ls shows a ecryptfs-mount-private.desktop symbolic link to /usr/share/ecryptfs-utils/ecryptfs-mount-private.desktop
- all files and directories from real <user> encrypted directory are missing

The disk is one partition

UUID=9b12bd21-53d4-38f5-c474-674e05cd8d7c / ext4 rw,relatime,discard,errors=remount-ro,data=ordered 0 1

cdir@host:~$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04

cdir@host:~$ apt-cache policy ecryptfs-utils
ecryptfs-utils:
  Installé : 104-0ubuntu1
  Candidat : 104-0ubuntu1
 Table de version :
 *** 104-0ubuntu1 0
        500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.2
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Thu May 29 23:09:28 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20130203-1
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-10-13 (228 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to trusty on 2014-05-29 (0 days ago)
VarLogDistupgradeTermlog:

Dash (devel-tootai) wrote :
Dash (devel-tootai) wrote :

Proble is worth then that: ones logged, my session gets out of the home ecrypted directory, have to run "ecryptfs-mount-private" from within a terminal or to close my session, restart lightdm, wait few seonds (around 20) and login again. Could be related to screensaver or hibernate features

Dash (devel-tootai) wrote :

After investigation, seems more a systemd problem: when I try to mount a sshfs file system in my X session, thinks are going bad. Still OK in console tty1 to 6 :-(

Dash (devel-tootai) wrote :

Addendum: console is also broken.

affects: ubuntu-release-upgrader (Ubuntu) → ecryptfs-utils (Ubuntu)
Dash (devel-tootai) wrote :

This bug is annoying, nobody uses ecryptfs?

I think the problem comes when an sshfs file system is mounted inside the home directory. For instance I have /home/dash as ecryptfs home directory, and inside I mount 'sshfs remoteServer:myDirectory myDirectory'

Then, when I navigate into the local myDirectory, the ecrypts filesystem shutdown; I have to give back credentials for the 'ecryptfs-mount-private' command, make 'cd' to be back in my home, umount the sshfs filesystem and then restart it. Can be 10 time in 5 minutes as well as 5 times a day ... If it arise too many times, ecryptfs refuses to mount the home directory and I have to restart the computer :-(

Dash (devel-tootai) wrote :

The problem is coming with ANY file system mounted inside the ecrypts directory. I faced the problem with an SMB file system.

I removed ecryptfs, since then all is good.

Regards

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers