After some debugging and testing I've narrowed the problem down to the fact that when using:
1. Secure NFS for $HOME 2. Kerberos authentication 3. The Kerberos ticket expires 4. Which causes $HOME to be unavailable. At this state this causes 'xscreensaver' to fail you try to awaken it (moving the mouse, pressing a key) when it starts the subprocess 'xscreensaver-lock' (that prompts the user for the password) since _that_ program can't read $HOME/.Xauthority which it needs to be able to open a connection to the X server... Ie, this isn't a problem with NFS (or Secure NFS) but rather a combination of problems with Secure NFS, Kerberos, how X authentication works and how xscreensaver works... -- This message posted from opensolaris.org
