public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Franz Fehringer <fehrin@googlemail.com>
To: cygwin@cygwin.com
Subject: Re: XWin problem (xinit launche twice)
Date: Sun, 24 May 2020 14:20:20 +0200	[thread overview]
Message-ID: <0a3630d2-1ce3-e011-d837-22ee76434c02@gmail.com> (raw)
In-Reply-To: <0196314e-7d02-a34a-7f2d-ae1d4f319d39@gmail.com>

Am 21.05.2020 um 21:38 schrieb Marco Atzeri via Cygwin:
> On 21.05.2020 20:07, Franz Fehringer wrote:
>> There is maybe a race (condition) i just managed starting xinit only
>> once (where it was started twice all the time).
>>
> 
> A race it is possible.
> 
> Sometimes I see xinit or Xwin stuck and I need to kill X,
> while the second time goes fine.
> 
> May be in your case the first is stuck and a second istance is
> risen again.
> 
> 
> Running starxwin from mintty is more likely to work for me
> the first time. I assume the AV is causing a delay in loading
> the libraries and the second repetition takes less time and avoid the
> race.
> 
> Regards
> Marco

Hi Marco,

Thx again for your advice and effort.
There seemingly is not much i can do.
What mechanism would start a second xinit instance?
I start clean (no xinit / XWin around) and have two xinitS in the next
second already.

Best regards

Franz

      reply	other threads:[~2020-05-24 12:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 10:15 Franz Fehringer
2020-05-17 10:23 ` Marco Atzeri
2020-05-17 11:00   ` Franz Fehringer
2020-05-17 16:42     ` Marco Atzeri
2020-05-21 17:50       ` Franz Fehringer
2020-05-21 18:00         ` Franz Fehringer
2020-05-21 18:07         ` Franz Fehringer
2020-05-21 19:38           ` Marco Atzeri
2020-05-24 12:20             ` Franz Fehringer [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=0a3630d2-1ce3-e011-d837-22ee76434c02@gmail.com \
    --to=fehrin@googlemail.com \
    --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).