Package: ecryptfs-utils
Version: 87-1
Severity: important

I have been having an odd issue with an ecryptfs home directory over
the past several days that I am at a loss to explain: I will somewhat
regularly be working and find that my home has unmounted itself.
It vanishes from the mount table without an apparent trace.

I have looked at the dmesg and log files when this happens and cannot
explain it.  I am particularly confused as to how it is possible for the
unmount to even happen, as I believe I have had open files at the time of
the unmount--but then again, I can manually run ecryptfs-umount-private
while logged in without complaint, which seems counterintuitive.

In fact, it just did it again while I was working on this bug report.
I was running nothing but terminal sessions at the time.

Up until a few days ago this had not been a problem; I have been an
ecryptfs home user for years now in Ubuntu and a good month plus in
Debian unstable.

Any guidance for gathering more information is much appreciated.

Of possible note is the fact that I am running GNOME 3 packages from 
experimental.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (150, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ecryptfs-utils depends on:
ii  gettext-base    0.18.1.1-4
ii  keyutils        1.5.2-2   
ii  libc6           2.13-18   
ii  libecryptfs0    87-1      
ii  libgpg-error0   1.10-0.3  
ii  libgpgme11      1.2.0-1.4 
ii  libkeyutils1    1.5.2-2   
ii  libnss3-1d      3.12.11-2 
ii  libpam-runtime  1.1.3-2   
ii  libpam0g        1.1.3-2   

ecryptfs-utils recommends no packages.

Versions of packages ecryptfs-utils suggests:
pn  cryptsetup    2:1.3.0-3
pn  opencryptoki  <none>   

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to