[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



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. 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 processes that still think they are 
running - and then keeping $HOME open.

If you could modify the startkde script (take a backup copy first)
and just before the final "echo 'startkde: done'" line, add some lines to 
generate some output. You need lsof (from the lsof package).

lsof > /tmp/openfiles  #this is unsecure if it is a multiuser box
ps x > /tmp/processes  #this is also unsecure if it is a multi user box

that way, we can see what processes exactly that keeps it open.

if you could try it a couple of times to make sure it is the same processes, 
it would be really nice.

/Sune
-- 
Genius, I'm not able to telnet to a proxy from Windows or from the file inside 
Word NT, how does it work?

You must ping to a clock over a graphic mouse.

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: