From: "Kunz, Christopher L" <clkunz@sandia.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [EXTERNAL] Re: startxwin - xinit unable to connect to X server
Date: Fri, 15 May 2015 18:01:00 -0000 [thread overview]
Message-ID: <eebc5010a7b24659802d36fe4c00c574@ES12AMSNLNT.srn.sandia.gov> (raw)
In-Reply-To: <55561D71.4020308@dronecode.org.uk>
After installing the 64 bit version of Cygwin, I don't experience this problem.
Backtrace output:
$ gdb --args /usr/bin/Xwin -multiwindow
GNU gdb (GDB) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/Xwin...(no debugging symbols found)...done.
(gdb) handle SIGSYS nostop
Signal Stop Print Pass to program Description
SIGSYS No Yes Yes Bad system call
(gdb) r
Starting program: /usr/bin/Xwin -multiwindow
[New Thread 8216.0x1470]
[New Thread 8216.0x22f8]
[New Thread 8216.0x1f34]
[New Thread 8216.0x1f70]
[New Thread 8216.0x1e90]
[New Thread 8216.0x2374]
gdb: unknown target exception 0x80000001 at 0x5dd96d61
Program received signal ?, Unknown signal.
[Switching to Thread 8216.0x2374]
0x5dd96d61 in sysfer!FirstHookFunc ()
from /cygdrive/c/Windows/SysWOW64/SYSFER.DLL
(gdb) bt full
#0 0x5dd96d61 in sysfer!FirstHookFunc ()
from /cygdrive/c/Windows/SysWOW64/SYSFER.DLL
No symbol table info available.
#1 0x00000000 in ?? ()
No symbol table info available.
(gdb)
Thanks.
-----Original Message-----
From: Jon TURNEY [mailto:jon.turney@dronecode.org.uk]
Sent: Friday, May 15, 2015 09:23
To: Kunz, Christopher L
Cc: cygwin@cygwin.com
Subject: [EXTERNAL] Re: startxwin - xinit unable to connect to X server
On 13/05/2015 19:40, Kunz, Christopher L wrote:
> After updating to the latest Cygwin distribution, I can no longer connect to X server. When I run startxwin (on a fresh Cygwin install), I get the following errors:
>
> xinit: giving up
> xinit: unable to connect to X server: Connection refused
> xinit: server error
>
> The XWin.#.log looks okay, I think (see attached). I've set DISPLAY to :0.0.
It seems that the X server is crashing while it's still starting up.
I'm afraid I can't reproduce this problem.
If possible, could you follow the "Generating a backtrace when the X server is crashing at startup" instructions at [1], which might shed some light on what is going wrong...
[1] http://x.cygwin.com/devel/backtrace.html
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
next prev parent reply other threads:[~2015-05-15 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 19:06 Kunz, Christopher L
2015-05-14 7:06 ` Bryan Berns
2015-05-15 16:37 ` Jon TURNEY
2015-05-15 18:01 ` Kunz, Christopher L [this message]
2015-05-15 19:08 ` [EXTERNAL] " Jon TURNEY
2015-05-18 16:43 ` Kunz, Christopher L
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eebc5010a7b24659802d36fe4c00c574@ES12AMSNLNT.srn.sandia.gov \
--to=clkunz@sandia.gov \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).