X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 04C38395B476 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1592115489; bh=El+inNoxAvck66O+H0xpmlVTu4JA425FUlDlus6wts4=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=f2oOln3l5rgxJfzp/Pv55qrN5BkwrQ0v++ywe1nMB963KTgkd13KK3lMeoyPlNevs t4YvlXYeCEMwzcyQo6wbL0EkSoSM4CFEbXQCzMXd4xsD+18LFeysui8yayvZ1n4q9F gycw9rYSD1v0buP3IwKAtWFc0qg2eHLx0eG5TGeU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 564E83840C23 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=BMqKqPxclKipPkacKX3tGUgjsciT+xNutrTsHfg14JU=; b=S11GgasxG1gDGf2bFBO2gHBkyk/ssY2O0Hs5xOx/YIvcdp5uTW4DlL74cWGPpabPh+ MmZpW0qoAx3qtlH1QbML+4NOkK0UdNX98SCAmkiegmxYSKyA1L4hI8QlhnUtGgPQ8HEW JzJWJ1MwcAF729ro0YBzIdPtfbXrOyWZzCbp1RUfW52r9zc8U2Vn/wFHaZKCrTNfuFAX twlM2/Osyhf8WBEj8oInTIWL6LhuwrLdGBemtcb/u4mV3qVoZi5zuH4G2TzR+BzGQVGr v07f180Bie5cqRNlo0H8IoZSM8GKgwoXIumi191hZLEWtyKhZtBCqpIUjg89OJ2r5gGv NQLw== X-Gm-Message-State: AOAM531EjClX3NeFJc224ExQXwOEkObfER1nLKCgOwxjQnpEjmP3A4Yy N70JVkty5m4KsEGAwrsWCYt+rIac X-Google-Smtp-Source: ABdhPJxuGfZQ/N05ZG63wnz/aiVUspPxVrGMzrhPzumtUmEvQj/TC5iitfNnUI4veo1DsH+jtMvzvg== X-Received: by 2002:a1c:6884:: with SMTP id d126mr6850266wmc.121.1592115484118; Sat, 13 Jun 2020 23:18:04 -0700 (PDT) Subject: Re: cygwin x11 doesn't start after windows 10 upgrade To: cygwin AT cygwin DOT com References: Message-ID: <44cf3ec8-7e7c-d6d2-cf85-b6363cc0d54f@gmail.com> Date: Sun, 14 Jun 2020 08:18:02 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: Content-Language: it X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_ASCII_DIVIDERS, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Marco Atzeri via Cygwin Reply-To: Marco Atzeri Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 05E6Ia5x032764 On 11.06.2020 17:57, Steinar Bang wrote: > 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. > > I have tried: > 1. Running xlaunch directly instead of double clicking config.xlaunch > 2. Running setup-86_64.exe to install all pending upgrades > 3. Running setup-86_64.exe to reinstall xlaunch > 4. Running setup-86_64.exe to reinstall xorg-server > > But none of this has made any difference. > > Does anyone have an idea what the problem might be? > > Here's XWin.0.log from a startup attempt: > https://gist.github.com/steinarb/dacfec5172fd547cbec7c87723163193 > > Thanks1 > > > - Steinar > Hi Steinar, forgot to ask, there is stackdump of Xwin ? usually the stack dump are under /usr/bin ls /usr/bin | grep stack but they can also be on your home directory or in other places. Re-looking at your Xwin.0.log ------------------------------------------------ XWin was started with the following command line: XWin :0 -multiwindow -clipboard -wgl ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1920 h 1080 winInitializeScreenDefaults - native DPI x 120 y 120 [ 24028.656] (II) xorg.conf is not supported [ 24028.656] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 24028.656] LoadPreferences: /cygdrive/d/Profiles/sbang/.XWinrc not found [ 24028.656] LoadPreferences: Loading /etc/X11/system.XWinrc [ 24028.656] LoadPreferences: Done parsing the configuration file... [ 24028.671] winDetectSupportedEngines - RemoteSession: no [ 24028.687] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [ 24028.687] winDetectSupportedEngines - Returning, supported engines 00000005------------------------------------------------ on my log the next record is winSetEngine - Multi Window or Rootless => ShadowGDI so it seems something is going wrong there from "man Xwin" I see two possible options for troubleshooting engine detection faults ------------------------------------------------------- -engine engine_type_id This option, which is intended for developers, overrides the server's automatically selected drawing engine type. This parameter will be ignored if the specified drawing engine type is not supported on the current system. Default behavior is to select the drawing engine with optimum perfor‐ mance that supports the specified depth and window configuration. The engine type ids are: 1 Shadow GDI 4 Shadow DirectDraw Non-Locking -------------------------------------------------------- on my system both options work, can you check on yours ? startxwin -- -engine 4 -- 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