X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=Nz yu6AgITYslzzbFixfgls8KMAIsuEoUB2j7XiD2ErJzLT15HqeFkbjkd78tlQpkbY DW6pyTNrINZAom8iumDW3aro1y843Kcw/LH+x4l8NtEhqJtstTDwPaBgU3A3NJmC Gjjjbz0Y+9S8EHSopBqbJlmaUZw0rwecJh+JfF5Ro= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=kr5RW5l1 BtpMntNSEjI5Ia0OSHA=; b=oAZ6FdrtvZJk0s/nA0/KfcvpbeAD3F6+rhEDrqZH cX8VID+2I0I3jqcDiiWvV6nX4gC5LJYJBcBQIJA3vmpUS8xsQ0Yfp6J/i1b3FrCR H6Lpik7pDeYaarC/BFBDYODmvdWw5IWDyZPaMdAUX3kRVKAY8HcJGne5CDEZnVt7 hzg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-yk0-f177.google.com MIME-Version: 1.0 X-Received: by 10.170.131.193 with SMTP id x184mr428586ykb.42.1437537694765; Tue, 21 Jul 2015 21:01:34 -0700 (PDT) In-Reply-To: <55AF0A76.5050202@bellsouth.net> References: <55ADCFFE DOT 2050208 AT bellsouth DOT net> <55AF0A76 DOT 5050202 AT bellsouth DOT net> Date: Wed, 22 Jul 2015 00:01:34 -0400 Message-ID: Subject: Re: Problems with cygwin in Windows 10 From: Michael DePaulo To: The Cygwin Mailing List Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Hi, (This is the same reply I sent when Robert emailed cygwin-xfree rather than cygwin.) On Tue, Jul 21, 2015 at 11:13 PM, Robert McBroom wrote: > > Having problems with the X interface in Windows 10 (currently build 10240). > /bin/startxwin fails with the symptoms in the attached file xwin.txt. The > output from cygcheck -cv is also attached. What am I missing? I have been using Cygwin/X on Windows 10 64-bit without issue, across numerous builds (currently 10240 also.) The 2nd time you ran startxwin, It looks like Cygwin thinks you lack 3D acceleration. Try this command: $ startxwin -- -extension GLX -multiwindow Also, the "UnknownGroup" might be an issue that prevented you from writing the lock file to /tmp/. Someone else would know better than me though. -Mike -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple