public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Holger, Vodafone" <holger.dietze@vodafone.de>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>, Steinar Bang <sb@dod.no>
Subject: Re: cygwin x11 doesn't start after windows 10 upgrade
Date: Fri, 26 Jun 2020 11:15:42 +0200	[thread overview]
Message-ID: <7AC92107-9216-4B3F-AED3-7BC63C61858C@vodafone.de> (raw)
In-Reply-To: <E82B95D3-AD0F-42DF-814D-75073B7A5BA2@vodafone.de>

Update: Solution:

When changing the execution mode of C:\cygwin64\bin\XWin.exe to „Windows 7 Compatbility“ the start of XWin work.

There is no Virus Blocking of TrendMicro but an incompatibility (no block message in TM). 

Regards, Holger

> Am 16.06.2020 um 13:46 schrieb Holger, Vodafone <holger.dietze@vodafone.de>:
> 
> Nothing changes (as expected) when running with logverbose 3
> 
> OsVendorInit - Creating default screen 0
> winInitializeScreens - 1
> winInitializeScreen - 0
> winValidateArgs - Returning.
> (II) xorg.conf is not supported
> (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html <http://x.cygwin.com/docs/faq/cygwin-x-faq.html> for more information
> LoadPreferences: /home/holgdiet.ifc/.XWinrc not found
> LoadPreferences: Loading /etc/X11/system.XWinrc
> LoadPreferences: Done parsing the configuration file...
> winGetDisplay: DISPLAY=:0.0
> winDetectSupportedEngines - RemoteSession: no
> winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
> winDetectSupportedEngines - Returning, supported engines 00000005
> 
> 
> And now my prompt is back, no XWin process any more. I will now wait on our iternal IT
> The strace was already clear enough with the trendmicro dll …..
> 
> 
>> Am 13.06.2020 um 23:15 schrieb Jon Turney <jon.turney@dronecode.org.uk>:
>> 
>> On 13/06/2020 10:04, Steinar Bang wrote:
>>>>>>>> Steinar Bang <sb@dod.no>:
>>>> Platform: amd64, windows 10 10.0.18363 Build 18363,
>>>>          cygwin xorg-server 1.20.5-3, xlaunch 20160530-1
>>>> I start X11 by double clicking the following config.xlaunch:
>>>> https://gist.github.com/steinarb/8687e2113c601e061da909e75a180f39
>>>> After the reboot caused by a windows 10 upgrade, launching X11 using
>>>> xlaunch have stopped working.
>> [...]
>>> Is the problem that I'm using xlaunch?  From the version number it looks
>>> like it is from 2016?  Has the world change enough that it now longer
>>> works for launching x?
>>> What does people use to launch cygwin X these days?
>> 
>> Sorry to hear you are having problems. [1] lists the ways of starting the X server we think should work [2].
>> 
>> The simplest way to run the X server is using 'XWin' at a command line.
>> 
>> Does that work?  I'm guessing probably not.  Does it hang? Or exit after doing nothing? Does 'XWin -logverbose 3' produce any more information?
>> 
>> [1] https://x.cygwin.com/docs/ug/cygwin-x-ug.html
>> [2] (although some of the more complex DEs should probably be removed from that list, as they are unmaintained and probably broken)
>> --
>> Problem reports:      https://cygwin.com/problems.html
>> FAQ:                  https://cygwin.com/faq/
>> Documentation:        https://cygwin.com/docs.html
>> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
> 
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple


  reply	other threads:[~2020-06-26  9:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 15:57 Steinar Bang
2020-06-13  6:30 ` Marco Atzeri
2020-06-13  9:30   ` Steinar Bang
2020-06-13 11:22     ` Marco Atzeri
2020-06-13 12:00       ` Steinar Bang
2020-06-13 13:22         ` Marco Atzeri
2020-06-13 15:48           ` Steinar Bang
2020-06-13 16:44             ` Steinar Bang
2020-06-13 20:37       ` Andrey Repin
2020-06-13  9:35   ` Steinar Bang
2020-06-13  9:55     ` Steinar Bang
2020-06-13 11:31       ` Marco Atzeri
2020-06-13 12:03         ` Steinar Bang
2020-06-13 12:09           ` Steinar Bang
2020-06-13 13:14         ` Holger, Vodafone
2020-06-13 13:29           ` Marco Atzeri
2020-06-13  9:04 ` Steinar Bang
2020-06-13 21:15   ` Jon Turney
2020-06-14 10:44     ` Steinar Bang
2020-06-14 11:18       ` Henry S. Thompson
2020-06-14 16:12         ` Steinar Bang
2020-06-14 17:49           ` Marco Atzeri
2020-06-14 21:45             ` Steinar Bang
2020-06-14 22:21               ` Holger, Vodafone
2020-06-15 12:17                 ` Holger, Vodafone
2020-06-15 12:57                   ` Holger, Vodafone
2020-06-16  4:22                   ` Brian Inglis
2020-08-02 20:25                   ` Steinar Bang
2020-08-02 21:00                     ` Eliot Moss
2020-08-04 12:01                       ` Steinar Bang
2020-08-04 13:12                         ` Hamish McIntyre-Bhatty
2020-08-04 16:55                         ` ASSI
2020-06-16  4:59                 ` ASSI
2020-07-02 15:01               ` Steinar Bang
2020-07-02 22:12                 ` Holger, Vodafone
2020-06-16 11:46     ` Holger, Vodafone
2020-06-26  9:15       ` Holger, Vodafone [this message]
2020-07-02 14:42         ` Steinar Bang
2020-06-14  6:18 ` Marco Atzeri
2020-06-14 10:38   ` Steinar Bang

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=7AC92107-9216-4B3F-AED3-7BC63C61858C@vodafone.de \
    --to=holger.dietze@vodafone.de \
    --cc=cygwin@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    --cc=sb@dod.no \
    /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).