I have done additional testing on this problem and it seems that the first user to login and run 'startxwin' owns all of the log and lock files and this is what is causing the problem. The first user can continue using xwin without issues, but no other users can do it after that.
If someone would upgrade xwin to to make these file names unique for each user it should solve the problem. Meanwhile, I'm envisioning several workarounds. -- View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29897721.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
