More info:

Running "cygcheck -rvs" from under bash (that I could only start from cmd.exe 
as shown earlier)
does not seem to show anything unusual (I have only single install of Cygwin, 
there's no conflict
of any kind, and all the packages check out Okay).

SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS

PWD = '/cygdrive/c/WINDOWS/system32'
HOME = '/'
CYGWIN = 'nodosfilewarning '
...
HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Installations
  (default) = '\??\C:\Cygwin64'
HKEY_CURRENT_USER\Software\Cygwin\setup
  (default) = 'C:\Cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
  (default) = '\??\C:\Cygwin64'

obcaseinsensitive set to 1

Cygwin installations found in the registry:
  System: Key: e022582115c10879 Path: C:\Cygwin64
  User:   Key: e022582115c10879 Path: C:\Cygwin64

c:  hd  NTFS    486939Mb  47% CP CS UN PA FC    QU  Local Disk
d:  cd             N/A    N/A
s:  net NTFS   2789212Mb  79% CP CS UN PA           [redacted]
u:  net NTFS     20480Mb  82% CP CS UN PA           lavr
x:  net NTFS   2789212Mb  79% CP CS UN PA           [redacted]
y:  net NTFS    116779Mb  60% CP CS UN PA       QU  lavr
z:  net NTFS    116779Mb  60% CP CS UN PA       QU  home

C:\cygwin64      /          system  binary,auto
C:\cygwin64\bin  /usr/bin   system  binary,auto
C:\cygwin64\lib  /usr/lib   system  binary,auto
cygdrive prefix  /cygdrive  user    binary,posix=0,auto

The only thing in that output that still does not seem right is this section
(which I can't show in its entirety, so I am redacting it):

Output from C:\cygwin64\bin\id.exe
UID: 1050182(NCBI_NT+User(1606)
GID: 1050182 groups=1050182,1049089(NCBI_NT+Group(513)
mote Desktop Users)
555(Remote Desktop Users)
545(Users)
...

Note that my username is still numeric and the second line shows some incomplete
group name that has been cut off in the middle ("mote Desktop Users")...
All other (about 20) groups that follow [...] have their numeric and textual
information correct, without any issues...

I vaguely remember having the same issue some time ago (but then my work PC was 
frequently bugchecking
because of a faulty memory module), and I did not tie any recent password 
change (if there was any at all)
with my unability to run Cygwin terminal...  That time I had to clean my 
registry settings pertaining
to Cygwin and then I got the terminal working back (still have a history of 
doing so in the support
ticket created back than).  I haven't done so just yet.  Maybe some other thing 
is also in the play here,
and I will gladly provide any necessary information while it persistently and 
reproducibly not working,
to have it fixed (rather than crudely worked around).

Thanks for looking into this.

Anton Lavrentiev
Contractor NIH/NLM/NCBI


-- 
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

Reply via email to