From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Subject: Re: Cygwin-X shortcut no longer works after recent updates
Date: Sat, 29 Feb 2020 14:15:00 -0000 [thread overview]
Message-ID: <dfe4417d-a5a3-81a9-747b-5fb7d8a2fe6c@dronecode.org.uk> (raw)
In-Reply-To: <9237e82b-d2c8-99ee-de23-0baf65816418@SystematicSw.ab.ca>
On 28/02/2020 07:21, 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.
Two copies of xinit suggests to me that it is getting stuck somewhere in
the cygwin fork/exec of /etc/X11/xinit/startxwinrc (which in turn starts
~/.startxwinrc if it exists) to start clients.
> On exiting the X server, the processes are left running and have to be killed off.
> There are sockets and lock files, which are left around after termination:
> $ llgo /tmp/.X11-unix/X0*
> srw-rw-rw- 1 0 Feb 27 23:11 /tmp/.X11-unix/X0=
> -rw------- 1 0 Feb 27 23:11 /tmp/.X11-unix/X0.lock
>
> The server log /var/log/xwin/XWin.0.log looks normal, and nothing shows in
> ~/.xsession-errors.
>
> My .startxwinrc is a copy of /etc/X11/xinit/startxwinrc with addition of the
> minnty terminal startup in bg before leaving xwin-xdg-menu running in fg.
>
> The shortcut and processes when started normally look like:
>
> C:\...\cygwin64\bin\run.exe --quote /bin/sh -l -c "cd; exec /usr/bin/startxwin"
> /bin/sh /usr/bin/startxwin
> \_ xinit /home/$USER/.startxwinrc -- /usr/bin/XWin ... [as below]
> \_ /usr/bin/XWin :0 -multiwindow -auth /home/$USER/.serverauth.$PGID
>
> I have checked the man pages and the Cygwin-X docs for hints about things to
> check and try with little success.
>
> Hints and suggestions about possible problems and problem solving approaches
> would be appreciated.
--
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
next prev parent reply other threads:[~2020-02-29 14:15 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 [this message]
2020-03-02 16:57 ` Henry S. Thompson
2020-03-02 18:36 ` Ronald Blaschke
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=dfe4417d-a5a3-81a9-747b-5fb7d8a2fe6c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--cc=cygwin@cygwin.com \
/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).