From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#31169: 26.1; Emacs 26.1 RC1 (gtk) display issues over SSH/X11 with xming/vcxsrv Date: Fri, 20 Apr 2018 08:05:12 -0400 Message-ID: <87h8o6rslj.fsf@gmail.com> References: <874lk8t4b6.fsf@gmail.com> <87y3hkrnn7.fsf@gmail.com> <834lk71ymx.fsf@gnu.org> <87k1t2spvb.fsf@gmail.com> <83604mz7uf.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1524225854 14016 195.159.176.226 (20 Apr 2018 12:04:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 20 Apr 2018 12:04:14 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) Cc: 31169@debbugs.gnu.org, charliehemlock@gmail.com To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Apr 20 14:04:09 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f9Ult-0003Xp-EV for geb-bug-gnu-emacs@m.gmane.org; Fri, 20 Apr 2018 14:04:09 +0200 Original-Received: from localhost ([::1]:52100 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f9Uo0-0002GL-0s for geb-bug-gnu-emacs@m.gmane.org; Fri, 20 Apr 2018 08:06:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46984) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f9Unl-0002Dw-Tu for bug-gnu-emacs@gnu.org; Fri, 20 Apr 2018 08:06:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f9Uni-000195-KI for bug-gnu-emacs@gnu.org; Fri, 20 Apr 2018 08:06:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:53895) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f9Uni-00018r-HQ for bug-gnu-emacs@gnu.org; Fri, 20 Apr 2018 08:06:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1f9Uni-0003l5-5p for bug-gnu-emacs@gnu.org; Fri, 20 Apr 2018 08:06:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 20 Apr 2018 12:06:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31169 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 31169-submit@debbugs.gnu.org id=B31169.152422592414399 (code B ref 31169); Fri, 20 Apr 2018 12:06:02 +0000 Original-Received: (at 31169) by debbugs.gnu.org; 20 Apr 2018 12:05:24 +0000 Original-Received: from localhost ([127.0.0.1]:33559 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f9Un6-0003k9-1t for submit@debbugs.gnu.org; Fri, 20 Apr 2018 08:05:24 -0400 Original-Received: from mail-it0-f43.google.com ([209.85.214.43]:52534) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f9Un1-0003jt-LD for 31169@debbugs.gnu.org; Fri, 20 Apr 2018 08:05:19 -0400 Original-Received: by mail-it0-f43.google.com with SMTP id f6-v6so2265446ita.2 for <31169@debbugs.gnu.org>; Fri, 20 Apr 2018 05:05:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=UZzVeXgVektSC2QU2bFiQFbC5yx1Foi6lfrY8JYi+4k=; b=RYTdI+ZeC/+je0T0uN/t3aVqgEvXGi577w3rX+Oetqpy6o9Frzn31AYRYxObKOTlaZ VYiXU1jsrdfc21jNzyNOUbKuXcIPm/PNM3IMBcLAboq+a91xYb7GiUTn9rocGiDceCxa y/q44QeBVFl+pYcROPoMS/pOme0D8okEgn7yY5BM7j4MYpGsMJ9xfCBOeNjcS+CdA/ca RKkOCnSmvRApaDcFqOQLKYMOcZOHdp2C66C+JTyzuCDHXG7sAw3BQxFKVM1008L6ax2i WlY3urS108AXtjSvCmISZLK7dTP2KyqiYRvtZVomLZk198/jKBJfr6+avrxeXvvRGBHi i6ew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=UZzVeXgVektSC2QU2bFiQFbC5yx1Foi6lfrY8JYi+4k=; b=FEI/K5ni2FZvsf32/ArV5qRR/O8dCOfHQNG0eKBLGAAM9yho3YWyuKs9xopQybs/dn 86tqTc67OKzjQ8DaLGQcMcHNNX+1+83GTbBVGlj1hoJ4sChPUwXbqN/ZmxZIKj6qcT63 LCyxCngbJvXYzWBHLm+zaTwmsg4aSHgyvVt4kqiqkS3pgVtPObKGmyQOgb5Qqym3Tmzl WdC/1Dt7aYZ4N0s2K/38ynrxtjIbiM2Qut8A4ULsreaLZuOlcv5op3Ta6tZZnJzJjiPx zXFk51l5P33T1pD9a0qCUcMeU/pF/eVstMLRkXF0TkritxpSF30D4rwBBRlXVHSqeOod ubig== X-Gm-Message-State: ALQs6tBjPNqnumvCFTfKcj5Xx6YblXhSmt5Yzu7hkFTPxCeeC8zVIdYN TpkFH+F4qM8EM2r45gKm8tE= X-Google-Smtp-Source: AIpwx4+A9PB+xgWfqxqPthqSLFDRPgxsEh0Zj1lZ2FxWq0Soe4TW6Vlv6vLrSlwEg7ZY8ShOIWV0UQ== X-Received: by 2002:a24:3694:: with SMTP id l142-v6mr2596139itl.83.1524225914240; Fri, 20 Apr 2018 05:05:14 -0700 (PDT) Original-Received: from zebian (cbl-45-2-119-34.yyz.frontiernetworks.ca. [45.2.119.34]) by smtp.googlemail.com with ESMTPSA id d65-v6sm2934756iod.54.2018.04.20.05.05.13 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 20 Apr 2018 05:05:13 -0700 (PDT) In-Reply-To: <83604mz7uf.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Apr 2018 09:54:00 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:145639 Archived-At: Eli Zaretskii writes: > The logic that determines which startup screen to display is in > use-fancy-splash-screens-p. Something there causes Emacs to decide > the second situation cannot handle the fancy splash screen. Ah, `fancy-splash-frame' checks `frame-visible-p', which, for my window manager, depends on when I switch to the workspace. So it's the removal of the wait for visibility changes again (related to bugs #24091, #25521, and #29095). Although setting x-wait-for-event-timeout doesn't seem to affect this, maybe that's a bug. I guess for OP's case, the remote X display is just a bit slow, so the frame doesn't become visible in time.