Comment 4 for bug 259293

Finally happened again! My laptop was left alone, with the lid closed, for about half an hour, and when I came back it had unmounted.

daniel@daniel-eee:~$ tail /var/log/auth.log
Aug 24 14:17:01 daniel-eee CRON[12681]: pam_unix(cron:session): session opened for user root by (uid=0)
Aug 24 14:17:01 daniel-eee CRON[12681]: pam_unix(cron:session): session closed for user root
Aug 24 15:17:01 daniel-eee CRON[12749]: pam_unix(cron:session): session opened for user root by (uid=0)
Aug 24 15:17:01 daniel-eee CRON[12749]: pam_unix(cron:session): session closed for user root
Aug 24 15:39:32 daniel-eee su[12774]: Successful su for daniel by root
Aug 24 15:39:32 daniel-eee su[12774]: + ??? root:daniel
Aug 24 15:39:32 daniel-eee su[12774]: pam_unix(su:session): session opened for user daniel by (uid=0)
Aug 24 15:39:32 daniel-eee su[12774]: Mount of private directory return code [256]
Aug 24 15:39:32 daniel-eee su[12774]: pam_unix(su:session): session closed for user daniel
Aug 24 15:39:32 daniel-eee su[12774]: Mount of private directory return code [0]

The catch though - by the time I found this, I had no PID 12774 running still... So I don't know what did this. Suffice to say, there is some program su'ing to me and then closing the session immediately. Maybe you know more?

Possibly the best way to close this 'bug' is to change the default behaviour away from auto umounting on any pam logout... Since it seems that there is at least one package easily installable in the default repo's that will cause the behaviour above.