Bug#425314: $HOME still in use after session has been closed - Steps to reproduce

2007-05-28 Thread Jan Engelhardt
Following might be helpful `strace -fe execve startkde` (or startx, or in .xinitrc) and `fuser -m /my/home/dir` Shouldn't the PAM session (which triggers libpam-mount to umount) only be closed after the X session has been closed, ie after the above processes have exited? The

Bug#425314: $HOME still in use after session has been closed - Steps to reproduce

2007-05-27 Thread Sune Vuorela
On Sunday 27 May 2007, Christian Kastner wrote: I installed etch on a spare partition of another computer, and I have the problem there as well. Below you will find the steps to reproduce the problem. If you now login and logout again, umount and removal of the encrypted device will fail.

Bug#425314: $HOME still in use after session has been closed - Steps to reproduce

2007-05-27 Thread Christian Kastner
Sune Vuorela wrote: If you now login and logout again, umount and removal of the encrypted device will fail. Enabling debug mode in /etc/security/pam_mount.conf will show three kdeinit processes keeping $HOME and $HOME/.xsession-errors open. First step is to figure out which kdeinit

Bug#425314: $HOME still in use after session has been closed - Steps to reproduce

2007-05-26 Thread Christian Kastner
I installed etch on a spare partition of another computer, and I have the problem there as well. Below you will find the steps to reproduce the problem. 1) Install Debian etch. Select only Standard in the tasksel dialog. 2) After reboot, install the following packages / meta-packages: *