From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18980 invoked by alias); 24 Jun 2019 07:28:54 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 18973 invoked by uid 89); 24 Jun 2019 07:28:54 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*c:alternative, View, uploaded X-HELO: mail-lf1-f54.google.com Received: from mail-lf1-f54.google.com (HELO mail-lf1-f54.google.com) (209.85.167.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 24 Jun 2019 07:28:52 +0000 Received: by mail-lf1-f54.google.com with SMTP id a9so9246379lff.7 for ; Mon, 24 Jun 2019 00:28:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+i53jNWgll0lmF5JnyomgjIKrlvvxik2z8rqyfF6e8I=; b=ZcrtnSRbz2ACvBeEpEWv/Q1GqmH8zL4s1nZC41eGbv1plPTxoRLVpmyDR66NF8Q67H kjUOHaANOLBmT410EwdXCgj83WcMU1QtMhqKXKIM6iGCKjtwbhjXsd8PRqQ+Lqg8j8Bw VSxcHRD+Ow6Bjn3st7WBcq+KrePgTww9hnc17gWqACQ0O2NcMx5TdzFT5fEMoE1H1wR7 WCQ19RmLeJghzRP2Bhbw0m7D/om0d7ygb2V/dMrtSfvnZGb8/bQcjDAiywKImiZlQioJ BPpBInblzndVZVPXblSdaRtIXF80k1aqTtYWLAiZpk4PxciRuT1c6mFRdnRHs4lsHqZM pVcg== MIME-Version: 1.0 References: <5fa8b89e-1a9d-2619-f49f-c1680d587148@dronecode.org.uk> In-Reply-To: From: Philippe Date: Mon, 24 Jun 2019 07:28:00 -0000 Message-ID: Subject: Re: Bug in libX11 or something near ? To: Jon Turney Cc: The Cygwin Mailing List Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00206.txt.bz2 Hi Jon, I just tested your snapshot on some software (including k3b, paraview and some others), and no more crashes ! Thanks a lot for this fix :) I guess you can release it on cygwin asap ! Thanks again for this fast work. regards, Philippe On Sun, Jun 23, 2019 at 8:41 PM Philippe wrote: > Hi Jon, > glad to view an answer ! > Just for your information, since I posted, I did some others tests, and I > can reproduce it with k3b (which use qt4) but NOT with kcalc (which use > qt5). > Then I tried some little python tests from Envisage for qt5 and wasn't > able to reproduce this crash. > > So I guess there's something wrong with qt4. > > Tomorrow I'll try your snapshot to confirm or not your fix ! > > Thanks for your time. > > On Sun, Jun 23, 2019 at 7:57 PM Jon Turney > wrote: > >> On 18/06/2019 17:07, Philippe wrote: >> > I'm using Cygwin/X and identified a critical bug using some piece of >> > software. >> > I don't really know where to begin, but I'm able to crash some >> applications >> > via the application's menu, only with Cygwin/X (no crash with Xming, >> and no >> > crash under any Linux distributions). >> > >> > For information, It goes through VirtualGL. I'll give the example on >> how to >> > reproduce it with a free software : Paraview (under linux). >> > >> > So you open Paraview, then clic on "View" > show the "Toolbars" submenu, >> > then you move your mouse directly on the "Sources" or "Edit" menu, then >> it >> > crashes immediately. The only error message in the linux shell (from >> where >> > it was launched) is "paraview: Fatal IO error: client killed". >> > >> > I got those lines in the XWin.0.log file : >> > SetupSysMenu: GetSystemMenu() failed for HWND 0x130746 >> > winTopLevelWindowProc - WM_DESTROY - WM_WM_KILL >> >> Thanks for reporting this problem, and the clear reproduction steps. >> >> This is an interesting bug in the Cygwin X server's multiwindow mode. It >> seems that under some circumstances, when removing a WM_TRANSIENT_FOR >> window which in turn had a child WM_TRANSIENT_FOR window (e.g. a menu >> which has a sub-menu), the X server's integrated WM would get confused >> and think that the main window had been closed (so terminating the >> application). >> >> I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps >> you could try that and see if it improves things for you? >> >> (I guessed you are using 64-bit Cygwin. If you need a 32-bit build >> instead, please let me know and I'll generate one) >> >> [1] >> >> ftp://cygwin.com/pub/cygwinx/x86_64/XWin.20190623-git-210c90b328cf8f18.exe.bz2 >> >> -- >> Jon Turney >> Volunteer Cygwin/X X Server maintainer >> > -- 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