art both 32 and 64 bit X.
Tatsuro
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/xterm-fails-after-update-cygwin-tp117317p117366.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.
On 09/04/2015 01:40, tmacchant wrote:
DISPLAY=:0.0 makes me to see xterm!
Note that so far I can share Cygwin/X for both 32 bit and 64 bit.
But now it should be started separately
(I am using both 32 bit and 64 bit version because I'm providing cvs
snapshot of gnuplot on both 32 and 64 bit.)
ssage in context:
http://cygwin.1069669.n5.nabble.com/xterm-fails-after-update-cygwin-tp117317p117349.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:
gwin.1069669.n5.nabble.com/xterm-fails-after-update-cygwin-tp117317p117348.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
U
On 08/04/2015 00:01, tmacchant wrote:
I have been able to X without problem before cygwin update.
From mintty window
*
$ xterm &
[1] 4740
$ xterm: Xt error: Can't open display: 127.0.0.1:0.0
*
What am I wrong for
ays starting up on DISPLAY 3.0
http://cygwin.1069669.n5.nabble.com/Xorg-server-always-starting-up-on-DISPLAY-3-0-td117063.html
Tatsuro
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/xterm-fails-after-update-cygwin-tp117317p117329.html
Sent from the Cygwin list mailing lis
t error: Can't open display: 127.0.0.1:0.0
*
What am I wrong for X?
Tatsuro
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/xterm-fails-after-update-cygwin-tp117317.html
Sent from the Cygwin list mailing list archive a
7 matches
Mail list logo