On 05/10/2009 11:30, Fergus wrote:
The only difference is the Cygwin version. -61 works, -62 hangs.
Likewise.
But this is not the same problem. Being unable to start the Xserver
is not the same as being unable to start an Xterm.
> With everything up to date (cygwin, luit, xorg-server, ... --
see attached cygwin.srv) the command
~> run XWin -nolisten local -multiwindow &
fails with an instruction to view /var/log/XWin.0.log (attached) which
closes with
Fatal server error:
Can't read lock file /tmp/.X0-lock
If I simply revert to the cygwin1.dll from -61, leaving all else
unchanged, the command works just fine and xterm can be started with
~> /bin/xterm -display localhost:0.0
This problem has been reported a few times before, but we don't know
why it happens. You might try the suggestions in the FAQ [1] and see ifhtey
help.
If you have more information, please add it to the bugzilla for this issue [2]
It's interesting that this is apparently provoked by a change in cygwin DLL.
I see a few items in the ChangeLog which relate to link(), but nothing that
seems relevant...
[1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file
[2] http://sourceware.org/bugzilla/show_bug.cgi?id=9778
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
