Mail Archives: cygwin/2023/04/05/16:30:57
| X-Recipient: | archive-cygwin AT delorie DOT com
|
| DKIM-Filter: | OpenDKIM Filter v2.11.0 sourceware.org 913703857710
|
| DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
|
| s=default; t=1680726617;
|
| bh=KNCD3gvfLxz2qn+Fta6PNsZndEVGB7RVofE+aWHfjBE=;
|
| h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
|
| List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
|
| From;
|
| b=qAsqtDw42iALEUaW17gu2WWxx+NcgNMLJ0mjxNb1qqrWnANUrF1dh0sO+eDEDtyrm
|
| K3y121M+HUf4kDdkSx57UDp2LgTzgAnUzd0k0P23jTIaxA1eVkjsU6Ylb/Wd+nZaBs
|
| hFbICpFRkwJq2VvtKVzEcvCT+QWIyY+wuU/w89sg=
|
| X-Original-To: | cygwin AT cygwin DOT com
|
| Delivered-To: | cygwin AT cygwin DOT com
|
| DMARC-Filter: | OpenDMARC Filter v1.4.2 sourceware.org DF4DA3858D20
|
| X-Google-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed;
|
| d=1e100.net; s=20210112; t=1680726578; x=1683318578;
|
| h=content-transfer-encoding:to:subject:message-id:date:from
|
| :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc
|
| :subject:date:message-id:reply-to;
|
| bh=NHQe/ti6psY5k44UGijWZyar3NtySKRyP3Q3kw+GPnI=;
|
| b=tuDfiX9Ch/K8NOqOxpRGCc4oaKRAmZ7MotgNGfe5xci+N1SfMpDoH6BhEabOT4imqK
|
| wmfqDVJhZLZ77n5elPrHgCUWFhOcpMIic66hclle7a1PaPokuzzPLTPCbTfwPSHrVe8s
|
| zZBc9Y1YP3suDl/1r3Z8KXyX82lq37WhIQvvNPJYJc7w3WSlJtJwPdON2crH2sbnP0Uc
|
| Lkb7quUVP4Nb375N9Oe4j+szSKGsHvGnsZ1dQjVxg5iOJ6UrkuG0dF0YmkrXW6enYQIK
|
| fIDfJ8Tc2e0JMOVhwXec/RjZ+XiANsRdIr/X02D/kYmqSli/NTQ7YFgXZHPGAVhh+rgG
|
| fRWQ==
|
| X-Gm-Message-State: | AAQBX9dgF2r1URa8Fozw5fya3TWBAxQxP4m45d+SRqEsJcOTTiFlzl+C
|
| fv8IpZE3NCYsyKnpksvMRe6Vpup7MT4VdCVVBHZpb6oZ06Y=
|
| X-Google-Smtp-Source: | AKy350YUVlVZRV1g9L6TBIk0Qq5Ru8MxIDOT++Xvo+hRoh3b38fh3gbcMWvyjyuRE0zC6xcjny+flZ1sjgb2zSSfnHo=
|
| X-Received: | by 2002:a50:bb2b:0:b0:4fc:f0b8:7da0 with SMTP id
|
| y40-20020a50bb2b000000b004fcf0b87da0mr1922213ede.1.1680726578171; Wed, 05 Apr
|
| 2023 13:29:38 -0700 (PDT)
|
| MIME-Version: | 1.0
|
| References: | <CAJ_58ioyu9bDq_1xxRSfOTnG=D3Fwev3m87SiCds5B8iCcEgBA AT mail DOT gmail DOT com>
|
| <fb79d3f4-ef1e-cc9e-1596-6d76a8b73dfe AT Shaw DOT ca>
|
| <CAJ_58ir7cFbHcUeUoU3yaGT+zR7yUU9ehcerA4-voG3FtAFe=Q AT mail DOT gmail DOT com>
|
| <2074517c-9459-ecd7-b679-7f21045a7017 AT Shaw DOT ca>
|
| In-Reply-To: | <2074517c-9459-ecd7-b679-7f21045a7017@Shaw.ca>
|
| Date: | Thu, 6 Apr 2023 05:29:26 +0900
|
| Message-ID: | <CAJ_58irCbWHUcq8G1fca7uYZeZxq9UcEk6Z7y_R2ttp3jh8tLw@mail.gmail.com>
|
| Subject: | Re: Mintty terminal crashes after changing the default home via
|
| nsswitch.conf and launch in a new profile in Windows 11
|
| To: | cygwin AT cygwin DOT com
|
| X-Spam-Status: | No, score=1.4 required=5.0 tests=BAYES_00, BODY_8BITS,
|
| DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF,
|
| FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, KAM_NUMSUBJECT, RCVD_IN_DNSWL_NONE,
|
| SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.6
|
| X-Spam-Level: | *
|
| X-Spam-Checker-Version: | SpamAssassin 3.4.6 (2021-04-09) on
|
| server2.sourceware.org
|
| X-BeenThere: | cygwin AT cygwin DOT com
|
| X-Mailman-Version: | 2.1.29
|
| List-Id: | General Cygwin discussions and problem reports <cygwin.cygwin.com>
|
| List-Archive: | <https://cygwin.com/pipermail/cygwin/>
|
| List-Post: | <mailto:cygwin AT cygwin DOT com>
|
| List-Help: | <mailto:cygwin-request AT cygwin DOT com?subject=help>
|
| List-Subscribe: | <https://cygwin.com/mailman/listinfo/cygwin>,
|
| <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
|
| From: | Yuta SUZUKI via Cygwin <cygwin AT cygwin DOT com>
|
| Reply-To: | Yuta SUZUKI <suzuyu1729 AT gmail DOT com>
|
| Sender: | "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
|
| X-MIME-Autoconverted: | from base64 to 8bit by delorie.com id 335KUgF6020276
|
Thomas and Brian,
Thank you for your replies.
> Please also cross-test with another terminal, e.g. rxvt, or xterm (after running an X server).
--- I tried Cygwin/X in the same procedure. I tried only xterm but
then I found a clearer problem:
After I launch XWin server, I got no response for
"Right-clicking on the "X applications menu" icon in the notification area".
Also, almost all windows get hung up (no normal response for GUI actions).
I can use only keyboard actions to manipulate applications.
Of course, again, signout & re-signin solve the problem completely.
Once I got some warning message, saying "please contact cygwin
developers" or like,
but I couldn't reproduce it and I didn't screenshot it... It said
"/tmp/... is locked" or something similar.
> Are you sure that Windows setup, update, AV update, Edge update, and all the ...
--- The signout & re-signin can be done very quickly, which solves the problem
and so I don't think such applications disturbing the environment.
Also, I found the issue in my lab, but now testing in my private machine,
which is not connected to domain network.
Also, I found that to reproduce the mintty terminal hung up,
it's better to click the blank (I mean black part) part of the terminal window,
not the upper edge of the window. (Then the cursor stops blinking,
which is strange.)
Yours,
Yuta
2023年4月6日(木) 4:55 Brian Inglis <Brian DOT Inglis AT shaw DOT ca>:
>
> On 2023-04-04 20:56, Yuta SUZUKI via Cygwin wrote:
> > Thank you for your reply.
> > But I can't get the point so much...
>
> >> This setting example is only a suggestion, not meant to be used verbatim, and
>
> > --- Yes. In my lab, I use another path for the default home. This is
> > just a simple test configuration.
>
> >> means that, for each Windows account at setup or login, under the user's Windows
> >> home directory, you will create a literal "cygwin" subdirectory, to be mounted
>
> > ---- I think that usually cygwin automatically makes the directory
> > assigned as the default home in nsswitch.conf (and indeed it does).
> > I tried the same experiment with making C:\Users\test\cygwin manually
> > before launching cygwin, but the same crash is reproduced.
>
> >> When you change this field from the default, it is up to you to understand and support the setting.
>
> > ---- Well, I know that I want to assign the home directory
> > automatically to every user of my lab.
> > I don't know the internal structure of cygwin and so what I can do is
> > to only announce
> > "Do not use cygwin at your very first sign-in to the machine.
> > Re-sign-in before launching cygwin".
> > But I think this is a bit ridiculous...
>
> Perhaps wait until account initialization is complete before starting Cygwin
>
> >> Cygwin startup is probably waiting for an automounter to provide the directory here,
>
> > ---- Actually, in my experiment, cygwin does make the directory
> > C:\Users\test\cygwin
> > and even I could output cygcheck to C:\Users\test\cygwin\foo.out (or
> > /cygdrive/c/test/foo.out).
> > The problem is only in the crash of the window system.
> > Addendum:
> > Setting Windows environment variable HOME to be /cygdrive/c/users/test
> > works without the issue,
> > but it does affect another application in my lab as documented in
> > cygwin's users guide.
> Are you sure that Windows setup, update, AV update, Edge update, and all the
> other junk Windows runs has completed, and the account has been logged in, and
> that account setup has completed, before you start installing Cygwin, and before
> you start running Cygwin?
>
> Also be aware that if you are on a domain, to top process in each Cygwin process
> tree has to access the ADC to load up all the AD related info including all the
> group memberships and rights for the user.
> This can takes seconds to minutes, if the ADC is not on a close, fast LAN link.
> So wait until you see a Cygwin shell prompt before trying anything.
>
> Perhaps try with a more lightweight app like cmd, rather than File Explorer,
> which easily locks up systems.
> Normally switching to TaskMgr, seeing the issue with, and killing the File
> Explorer process tree, resets the system, and restarts File Explorer.
>
> During testing, switch to TaskMgr and check resource usage and waits to see what
> is actually causing the issue.
> It is often an app in Cygwin's BLODA Big List Of Dodgy Apps:
>
> https://cygwin.com/faq/faq.html#faq.using.bloda
>
> a "dodgy" app, often an AntiVirus, Malware, or other monitor, that is not
> written well enough to do its job without interfering with other apps.
>
> This especially applies to Cygwin as it has to work around Windows limitations
> at a low level to implement POSIX compatible syscalls, and AV and monitoring
> applications are not always well written.
>
> Do you have any such software operating on these systems, what is it, is it in
> our BLODA list; what is the system resource usage and what is in wait states
> when the issue occurs?
>
> --
> Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
>
> La perfection est atteinte Perfection is achieved
> non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
> mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
> -- Antoine de Saint-Exupéry
--
鈴木 雄太
立教大学 理学部数学科 助教
Yuta Suzuki
Department of Mathematics, Rikkyo University
suzuyu1729 AT gmail DOT com
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
- Raw text -