From: Ronald Blaschke <mailing-lists@rblasch.org>
To: cygwin@cygwin.com
Subject: Re: Cygwin-X shortcut no longer works after recent updates
Date: Mon, 02 Mar 2020 18:36:00 -0000 [thread overview]
Message-ID: <cdd3d45d-c2ce-6efd-eb6e-d8a709d1e581@rblasch.org> (raw)
In-Reply-To: <9237e82b-d2c8-99ee-de23-0baf65816418@SystematicSw.ab.ca>
On 2/28/20 8:21 AM, Brian Inglis wrote:
> Hi folks,
>
> After the recent upgrades to cygwin 3.1.4, perl, etc. I have found that the
> Cygwin-X Startup, Start Menu, and Task Bar shortcuts no longer work, although I
> can start Cygwin-X by running startxwin from a mintty window.
>
>From the shortcut, the shell is invoked to run startxwin normally, two copies of
> xinit fork, and Xwin runs and displays the start tray Xserver icon, but my
> mintty terminal and the xwin-xdg-menu clients don't start.
I think I am seeing the same problem. Here are a few observations.
1) The issue happens often, but not always, when starting with the
Windows shortcut. Currently, I am retrying a few times until the
startup works. I have been unable to reproduce the issue starting
startxwin from a mintty window.
2) XWin always seems to start fine.
3) If the issue comes up, I am always seeing the following hanging
process tree.
3969 cons0 S 0:00 \_ xinit ...
3970 cons0 S 0:00 \_ /usr/bin/XWin ...
3974 ? Ss 0:00 \_ /usr/bin/sh <defunct>
In Windows, this looks like so.
C:\cygwin64\bin\xinit.exe
\_ C:\cygwin64\bin\xinit.exe
\_ C:\cygwin64\bin\sh.exe
C:\cygwin64\bin\XWin.exe
Currently, I am killing the defunct sh, which seems to properly clean up
everything, and try again.
Ron
--
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
prev parent reply other threads:[~2020-03-02 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 7:21 Brian Inglis
2020-02-29 14:15 ` Jon Turney
2020-03-02 16:57 ` Henry S. Thompson
2020-03-02 18:36 ` Ronald Blaschke [this message]
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=cdd3d45d-c2ce-6efd-eb6e-d8a709d1e581@rblasch.org \
--to=mailing-lists@rblasch.org \
--cc=cygwin@cygwin.com \
--cc=ron@rblasch.org \
/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).