This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: [EXTERNAL] Re: startxwin - xinit unable to connect to X server
- From: "Kunz, Christopher L" <clkunz at sandia dot gov>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Mon, 18 May 2015 16:19:17 +0000
- Subject: RE: [EXTERNAL] Re: startxwin - xinit unable to connect to X server
- Authentication-results: sourceware.org; auth=none
- References: <4a3f92951e894d9abcc0f184ad983ba1 at ES12AMSNLNT dot srn dot sandia dot gov> <55561D71 dot 4020308 at dronecode dot org dot uk> <eebc5010a7b24659802d36fe4c00c574 at ES12AMSNLNT dot srn dot sandia dot gov> <5556348D dot 7040807 at dronecode dot org dot uk>
Looks like Jon was 100% correct. For me it appears to have been Symantec Endpoint Protection causing the problem. Updated / added exception and the problem has resolved.
Thanks!
-----Original Message-----
From: Jon TURNEY [mailto:jon.turney@dronecode.org.uk]
Sent: Friday, May 15, 2015 11:02
To: Kunz, Christopher L; cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: startxwin - xinit unable to connect to X server
On 15/05/2015 18:36, Kunz, Christopher L wrote:
> After installing the 64 bit version of Cygwin, I don't experience this problem.
>
> Backtrace output:
>
> 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.
The injected sysfer.dll belongs to "Symantec Endpoint Protection"
See [1] for a previous incident. As discussed there, I suggest you try updating SEP, or creating an exception for XWin.
[1] https://cygwin.com/ml/cygwin/2015-03/msg00080.html
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer