On 09/11/2010 09:02, Fergus wrote:
>>> Fatal server error:
>>> Can't read lock file /tmp/.X0-lock
>
>> Does /tmp/.X0-lock exists? Is it readable by you?
>
> Yes.
Hmm. It's strange that the Xserver should choose to lie about that, then.
The code in question really does just say...
lfd = o
>> Fatal server error:
>> Can't read lock file /tmp/.X0-lock
> Does /tmp/.X0-lock exists? Is it readable by you?
Yes.
> Are you sure /tmp is getting mounted successfully
> where you expect it to be?
Yes.
> Have you tried '-nolock', as suggested by [1]
I hadn't then.
But I have now and as a c
On 11/8/2010 6:48 AM, Fergus wrote:
PS It kills me not to copy this to cygwin at cygwin dot com which I feel will
have a much wider readership and skill set amongst that readership, but
anybody sinning in this regard is always referred straight to Cygwin-X.
Because this is where those intereste
On 08/11/2010 11:48, Fergus wrote:
> Since the update I have been unable to start XWin under [1.7].
> Following my usual sequence at a bash prompt:
>
> mount n:/tmp /tmp # drive n: is NTFS as required
> run XWin -multiwindow &
>
> Normally these two would be followed by a command line for xterm,
Dear Jon,
Since the update I have been unable to start XWin under [1.7].
Following my usual sequence at a bash prompt:
mount n:/tmp /tmp # drive n: is NTFS as required
run XWin -multiwindow &
Normally these two would be followed by a command line for xterm, but I
am not getting that far! The s
The following packages have been updated in the Cygwin distribution:
*** xorg-server-1.9.2-1
*** xorg-server-dmx-1.9.2-1
These packages contain XWin and the other X.Org X11 servers.
In addition to upstream fixes, this contains the following cygwin-specific
changes since 1.9.0-2:
* Rewrite of t
