On 29/07/2014 00:57, Matt D. wrote:
Doh! I was so blind! Windows XP does not have an IPv6 protocol installed
by default. I added it and the problem went away.
This sounds like a bug. XWin should verify whether a device which
supports the target protocol exists before attempting to open a socket
Thanks for reporting this problem.
On 21/07/2014 18:30, Matt D. wrote:
I found as a workaround to add the arguments -nolisten tcp when
invoking xinit. However, I was under the impression that it was
incompatible with -multiwindow and -clipboard, both of which seem to be
working fine:
Doh! I was so blind! Windows XP does not have an IPv6 protocol installed
by default. I added it and the problem went away.
This sounds like a bug. XWin should verify whether a device which
supports the target protocol exists before attempting to open a socket
on it.
What is this used for?
Still hangs with the latest 1.15.1-4 release.
On my main machine, I get the following output:
$ xinit -- -displayfd 1
read display number ':0' from X server
0
On the VM it just hangs. Taskmanager shows xinit.exe waiting or hung
with XWin.exe churning cycles and eating memory; about 4kB a
Ok.. so I let xinit do its thing to see if it got anywhere. Eventually
it will pop and error box. Interestingly, I specified a displayfd value
of 3 and yet both the popup and the log are reporting 5:
http://oi58.tinypic.com/106fono.jpg
My XWin.0.log is about 15MB of repeated attempts to open
The operating system is Windows XP Professional. It is a CLEAN install
on a VMware virtual machine and is 100% patched up. Cygwin also is a
clean install. I did try a rebaseall with no effect.
This is the first time I've encountered this. When I run xinit --
-displayfd 3, xinit will hang and
