https://bugzilla.novell.com/show_bug.cgi?id=465955 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c40 --- Comment #40 from Suresh Jayaraman <sjayaraman@novell.com> 2009-02-25 05:38:49 MST --- I think I have found a pattern for consistently reproducing this problem. Atleast, I have been able to reproduce this way always on 11.0: On a nfs mounted home with KDE login, 1. open 2 xterm 2. from one of the xterm session, "ssh -X" to remote host 3. "stat ~/.Xauthority" on the remote ssh session (note the inode number) 4. close two xterm session 5. On the server "stat ~/.Xauthority" 6. Now on the client, try to open xterm (it will fail) After a few seconds/minutes you would again be able to open xterm I think this is what is happening: * Step 3 above ensures that ls output is cached on the client. * Step 5 above changes the inode number again without client's knowledge * During Step 6, client tries to access .Xauthority and gets -ESTALE, but since it is not clearing the cache (and/or) setting INO_STALE flag, it attempts a second ACCESS which also fails with -ESTALE. I will attach a patch to handle -ESTALE better soon. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.