X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B89E43853800 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca X-Authority-Analysis: v=2.4 cv=Ac10o1bG c=1 sm=1 tr=0 ts=61085c82 a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17 a=IkcTkHD0fZMA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 Subject: Re: Unable to start Cygwin64 terminal after password change To: cygwin AT cygwin DOT com References: From: Brian Inglis Organization: Systematic Software Message-ID: <771e99c7-19c5-df67-abf2-fefde0e4d7b5@SystematicSw.ab.ca> Date: Mon, 2 Aug 2021 14:58:41 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-CA X-CMAE-Envelope: MS4xfBIBZJGpgdrP2m8ippQ73916+gKJj6TGzVc55x5AeiUvZjzT7qEdJrIeY0ZnUfFX9Gon1/9qw/XLr70+WdqyZGrhLnAvl/Y7wasIi2/FhS9KA0F0ooum zSHWf9muC/VWd7vMC71StX5R7AvfISVm3k8Sld8TkaxtLjcy+AENFTy88yYDo+VGfzElu9XCUFdmUrN0lxnvXOPEjzpW7VrQnrg= X-Spam-Status: No, score=-1161.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: cygwin AT cygwin DOT com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On 2021-08-02 12:31, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: >> I'll follow up once I have the output you've requested. > > Well, my Systems people stopped cygserver for me, and I was able to open the "Cygwin64 terminal" without problems... The machine wasn't rebooted, re-login'ed, nothing. > > So cygserver was the culprit? > > When I run id now, I get it all correctly, from both that very terminal: > > $ id > uid=1050182(lavr) gid=1049089(Domain Users) groups=1049089(Domain Users),555(Remote Desktop Users),545(Users),559(Performance Log Users),14(REMOTE INTERACTIVE LOGON),4(INTERACTIVE).... > > and also from "bash" that I used to start from "cmd.exe" (when the terminal wouldn't open up): > > C:\Windows\System32>cd \cygwin64\bin > > C:\Cygwin64\bin>bash > > lavr AT NCBIPC9135 /usr/bin > $ id > uid=1050182(lavr) gid=1049089(Domain Users) groups=1049089(Domain Users),555(Remote Desktop Users),545(Users),559(Performance Log Users),14(REMOTE INTERACTIVE LOGON),4(INTERACTIVE),11(Authenticated Users),15(This Organization),4095(CurrentSession)... > > Also note that my prompt is not showing anything numeric anymore... > > Any clues? All Cygwin services need to be shut down prior to running Cygwin Setup and they need to be restarted after Cygwin Setup completes successfully. If Cygwin services are running while Cygwin Setup is running, Cygwin components in use can not be updated, and you should get a Restart to update prompt. If you can not control the services, you should not run Setup: it should all be packaged into a script run elevated by those who have control. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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