xterm fails even when DISPLAY is set

Hi,

I have just installed cygwin-1.5.19, and cannot open an xterm.

I start the XWin server and the task manager shows that XWin.exe is
running. When I type "xterm" on the command line nothing happens - no
window appears and no error message is reported. The return status from
the xterm command in 53.

XWin is started as follows:

$ export DISPLAY=127.0.0.1:0.0
$ /usr/X11R6/bin/startxwin.sh 

The output is shown below, and also the log file /tmp/XWin.log

When I run xterm, nothing happens:

$ xterm
$ echo $?
53

When cygwin was installed I simply installed everything - I didn't
attempt to do a customised install ie. omitting certain packages etc.
However I have found that some utilities like "/usr/bin/less" and
"/usr/bin/tbl" were missing, so I installed the "less" and "groff"
packages. Maybe that indicates my install is not complete?

I have tried the "twm" window manager and it too fails:
$ twm

Re: xterm fails even when DISPLAY is set

On 9/1/06, Jeffrey Stephen <Stephen.Jeffrey <at> nrm.qld.gov.au> wrote:
> Hi,
>
> I have just installed cygwin-1.5.19, and cannot open an xterm.
>
> I start the XWin server and the task manager shows that XWin.exe is
> running. When I type "xterm" on the command line nothing happens - no
> window appears and no error message is reported. The return status from
> the xterm command in 53.
>
> XWin is started as follows:
>
> $ export DISPLAY=127.0.0.1:0.0
> $ /usr/X11R6/bin/startxwin.sh
>
> The output is shown below, and also the log file /tmp/XWin.log
>
> When I run xterm, nothing happens:
>
> $ xterm
> $ echo $?
> 53
>

DISPLAY needs to be set for the client programs, not for the X server. Try:
$ export DISPLAY=:0
$ xterm

--

-- 
Justin Patrin

Re: xterm fails even when DISPLAY is set

Cygwin Error

Dear Sir/Madame,

         Upon issuing the command

                 startxwin.bat

         I receive an error message saying:

         "A fatal error has occurred and Cygwin/X will now exit.
         Please open /tmp/XWin.log for more information."

         But Cygwin does not exit.

         The log states:

         "Fatal server error.
         Cannot establish any listening sockets."

         Can you please help me understand this problem and make the
appropriate correction?

Thank you,
Ron Duchovic

Ronald J. Duchovic, Ph.D.
Associate Professor of Chemistry
Indiana University Purdue University Fort Wayne
260-481-6293 (Office)
260-481-6070 (FAX) 

--
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/

Re: Cygwin Error

Ronald J. Duchovic wrote:
> Dear Sir/Madame,
>
>         Upon issuing the command
>
>                 startxwin.bat
>
>         I receive an error message saying:
>
>         "A fatal error has occurred and Cygwin/X will now exit.
>         Please open /tmp/XWin.log for more information."
>
>         But Cygwin does not exit.
>
>         The log states:
>
>         "Fatal server error.
>         Cannot establish any listening sockets."
>
>         Can you please help me understand this problem and make the
> appropriate correction?
>
> Thank you,
> Ron Duchovic
>
> Ronald J. Duchovic, Ph.D.
> Associate Professor of Chemistry
> Indiana University Purdue University Fort Wayne
> 260-481-6293 (Office)
> 260-481-6070 (FAX)
>
>
It seems like a firewall/virus scanner/security software issue.  Try
disabling them, and try again.  And please, the next time you report a
problem, remember:
> Problem Reports: http://cygwin.com/problems.html

--
Charli
---
Why do you ask me?  I don't even know who's thread this is!

Re: Cygwin Error

Ronald J. Duchovic wrote:

>         Upon issuing the command
> 
>                 startxwin.bat
> 
>         I receive an error message saying:
> 
>         "A fatal error has occurred and Cygwin/X will now exit.
>         Please open /tmp/XWin.log for more information."
> 
>         But Cygwin does not exit.

What do you mean, the terminal doesn't close? that's normal, the process that
will terminate (exit) is XWin which runs in the background.

>         The log states:
> 
>         "Fatal server error.
>         Cannot establish any listening sockets."
> 
>         Can you please help me understand this problem and make the
> appropriate correction?

Could be a permission problem, the user does not have the necessary permissions
to open the required ports (this happens in Unix, I've never seen it in Cygwin).
 Is your user a member of the PowerUsers or Administrators group?

What version of Windows are you using?
--

-- 
René Berber

--
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/

startx failure, on fresh install

startx won't start X, after fresh install of latest cygwin on fresh XP 
laptop

See previous report here:

http://cygwin.com/ml/cygwin-xfree/2006-08/msg00099.html

(no responses to that). I've found one other user with exactly the same 
problem, but have had no response in this forum or in the cybertechhelp 
forum where the other user posted, so I'm posting again.

Currently, my options seem to be:
(1) go buy another laptop, maybe cygwin-x will work on that one. I kind 
of like this one, though, everything else works on it.
(2) attempt to 'downgrade' from 6.8.99 to 6.8.1 / 6.8.2 (there's a mix 
of these available on the mirrors); I've seen one report by a user who 
had success fixing a similar issue by this means. Is there anythng I 
should know before I try this? It seems that setup.exe will refuse to 
change all the X components at once, in particular the xorg-x11-base 
needs to be changed separately. Do I change it first, or last? My 
previous experience with this sort of thing makes me concerned that I'll 
irrevocably mess up my install if I do this wrong.

--
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/

Re: startx failure, on fresh install

gsmith <at> alumni.uwaterloo.ca wrote:
> 
> startx won't start X, after fresh install of latest cygwin on fresh XP
> laptop
> 
> See previous report here:
> 
> http://cygwin.com/ml/cygwin-xfree/2006-08/msg00099.html
> 
> (no responses to that). I've found one other user with exactly the same
> problem, but have had no response in this forum or in the cybertechhelp
> forum where the other user posted, so I'm posting again.
> 
> Currently, my options seem to be:
> (1) go buy another laptop, maybe cygwin-x will work on that one. I kind
> of like this one, though, everything else works on it.
> (2) attempt to 'downgrade' from 6.8.99 to 6.8.1 / 6.8.2 (there's a mix
> of these available on the mirrors); I've seen one report by a user who
> had success fixing a similar issue by this means. Is there anythng I
> should know before I try this? It seems that setup.exe will refuse to
> change all the X components at once, in particular the xorg-x11-base
> needs to be changed separately. Do I change it first, or last? My
> previous experience with this sort of thing makes me concerned that I'll
> irrevocably mess up my install if I do this wrong.
> 
> 
> 
> 
> 
> 
> 

You may want to use startxwin.sh or startxwin.bat, since there seems to
be no evidence of anybody trying those methods yet.  My experience is
that I have tried startx and startxwin.sh, and they both don't work; the
startxwin.bat file is the only one that worked for me.  Try it out, and
see what happens.

And the next time you report a problem, you might want to read:
> Problem reports:       http://cygwin.com/problems.html

--
Charli
---
Step away from make 3.80.

Re: startx failure, on fresh install

Greg Smith wrote:
>> startx won't start X, after fresh install of latest cygwin on fresh XP
>> laptop
> 
>> See previous report here:
> 
>> http://cygwin.com/ml/cygwin-xfree/2006-08/msg00099.html
> 
>> (no responses to that). I've found one other user with exactly the same
>> problem, but have had no response in this forum or in the cybertechhelp
>> forum where the other user posted, so I'm posting again.
> 
>> Currently, my options seem to be:
>> (1) go buy another laptop, maybe cygwin-x will work on that one. I kind
>> of like this one, though, everything else works on it.
>> (2) attempt to 'downgrade' from 6.8.99 to 6.8.1 / 6.8.2 (there's a mix
>> of these available on the mirrors); I've seen one report by a user who
>> had success fixing a similar issue by this means. Is there anythng I
>> should know before I try this? It seems that setup.exe will refuse to
>> change all the X components at once, in particular the xorg-x11-base
>> needs to be changed separately. Do I change it first, or last? My
>> previous experience with this sort of thing makes me concerned that I'll
>> irrevocably mess up my install if I do this wrong.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> You may want to use startxwin.sh or startxwin.bat, since there seems to
> be no evidence of anybody trying those methods yet.  My experience is
> that I have tried startx and startxwin.sh, and they both don't work; the
> startxwin.bat file is the only one that worked for me.  Try it out, and
> see what happens.
> 
> And the next time you report a problem, you might want to read:
>> Problem reports:       http://cygwin.com/problems.html
> 

My apologies for the raw email address! 

Charli

Re: startx failure, on fresh install

>You may want to use startxwin.sh or startxwin.bat, since there seems to
>be no evidence of anybody trying those methods yet.  My experience is
>that I have tried startx and startxwin.sh, and they both don't work; the
>startxwin.bat file is the only one that worked for me.  Try it out, and
>see what happens.

Thank you for the response. startxwin.sh result seems identical to startx.
startxwin.bat actually starts the server, but it's not viable:

(1) run startxwin.bat in win command shell. X appears in sys tray.
(2) "env DISPLAY=127.0.0.1:0.0 xclock & " in a cygwin shell: no window opens.
(3) "env DISPLAY=127.0.0.1:0.0 xlogo &" in a cygwin shell: X window opens,
but if you breathe on it, an error occurs (if you hit 'return' in the cygwin
shell, or if you just alt-tab to the X window and back). Error message is

Xlib: sequence lost (0x10000 > 0x32) in reply type 0x0!
X Error of failed request:  0
  Major opcode of failed request:  0 ()
  Serial number of failed request:  0
  Current serial number in output stream:  50

I can also run 'XWin -multiwindow' in a cygwin shell, and get a similarly flaky X session.

> And the next time you report a problem, you might want to read:
> Problem reports:       http://cygwin.com/problems.html

Well I did, actually; the full error dump is in the previous report that I linked to,
and there's even more info (from another user with an identical problem) in a report
linked to from there. I didn't think it was useful to replicate the full dump, I had 
no new information.

And, re putting my full address in: no sweat, I get so much spam already at this
address it's doubtful it will make any difference.

--
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/