public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: cygwin@cygwin.com
Subject: Re: cygwin x11 doesn't start after windows 10 upgrade
Date: Sat, 13 Jun 2020 17:48:51 +0200	[thread overview]
Message-ID: <upzc8sgr6k64.fsf@dod.no> (raw)
In-Reply-To: <e6416099-8249-9240-0293-d9b59b7e7f04@gmail.com>

>>>>> Marco Atzeri via Cygwin <cygwin@cygwin.com>:
>>> It is never a good idea to have the Cygwin Home dir the
>>> same of Windows user dir

>> Why this not a good idea?

> because permissions like the one needed for ssh
> can be screwd by Windows ACL permission inherited

Ok.

FWIW I have used cygwin ssh for two things:
 1. Launching mosh sessions (this still worked after the Win10 upgrade)
 2. Running "ssh -Y " sessions from lxterminal launched with XWin by xlaunch
and it has worked fine until the reboot followed by the Win10 upgrade.

mosh still works, and normal ssh (without -Y) from cygwin terminals
still works, after the Win10 upgrade.

> can you reset the default

> db_home:  /home/%U

> close all processes and try X again ?
> This should use /home/sbang as your new home and
> we can see if it is a permission problem that is causing
> issue to Xwin

I changed the /etc/nsswitch.conf file, and rebooted to ensure all
processes had been killed.  But cygwin still seemed to use the
windows profile directory.  I still have HOME set to the profile
directory.  I have all of my unix-y program setup files there (used by
GNU emacs, git bash, and mingw utilities)

But still no luck in launching XWin, either with xlaunch or from the
command line.

I will unset HOME and reboot and try again.

For now, here's the output from the launch from the cygwin console:
sbang@ITEM-S63383:~$ pwd
/cygdrive/d/Profiles/sbang
sbang@ITEM-S63383:~$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
#    This file is read once by the first process in a Cygwin process tree.
#    To pick up changes, restart all Cygwin processes.  For a description
#    see https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch
#
# Defaults:
# passwd:   files db
# group:    files db
# db_enum:  cache builtin
db_home:  /home/%U
# db_home:  windows
# db_shell: /bin/bash
# db_gecos: <empty>
sbang@ITEM-S63383:~$ ll /home/sbang
ls: cannot access '/home/sbang': No such file or directory
sbang@ITEM-S63383:~$ pwd
/cygdrive/d/Profiles/sbang
sbang@ITEM-S63383:~$ startxwin

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.20.5.0
OS: CYGWIN_NT-10.0-18363 ITEM-S63383 3.1.5-340.x86_64 2020-06-01 08:59 UTC x86_64
OS: Windows 10  [Windows NT 10.0 build 18363] (Win64)
Package: version 1.20.5-3 built 2019-09-06

XWin was started with the following command line:

/usr/bin/XWin :0 -multiwindow -auth
 /cygdrive/d/Profiles/sbang/.serverauth.652

(II) xorg.conf is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
LoadPreferences: /cygdrive/d/Profiles/sbang/.XWinrc not found
LoadPreferences: Loading /etc/X11/system.XWinrc
LoadPreferences: Done parsing the configuration file...
winDetectSupportedEngines - RemoteSession: no
winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
winDetectSupportedEngines - Returning, supported engines 00000005
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
sbang@ITEM-S63383:~$


  reply	other threads:[~2020-06-13 15:49 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 15:57 Steinar Bang
2020-06-13  6:30 ` Marco Atzeri
2020-06-13  9:30   ` Steinar Bang
2020-06-13 11:22     ` Marco Atzeri
2020-06-13 12:00       ` Steinar Bang
2020-06-13 13:22         ` Marco Atzeri
2020-06-13 15:48           ` Steinar Bang [this message]
2020-06-13 16:44             ` Steinar Bang
2020-06-13 20:37       ` Andrey Repin
2020-06-13  9:35   ` Steinar Bang
2020-06-13  9:55     ` Steinar Bang
2020-06-13 11:31       ` Marco Atzeri
2020-06-13 12:03         ` Steinar Bang
2020-06-13 12:09           ` Steinar Bang
2020-06-13 13:14         ` Holger, Vodafone
2020-06-13 13:29           ` Marco Atzeri
2020-06-13  9:04 ` Steinar Bang
2020-06-13 21:15   ` Jon Turney
2020-06-14 10:44     ` Steinar Bang
2020-06-14 11:18       ` Henry S. Thompson
2020-06-14 16:12         ` Steinar Bang
2020-06-14 17:49           ` Marco Atzeri
2020-06-14 21:45             ` Steinar Bang
2020-06-14 22:21               ` Holger, Vodafone
2020-06-15 12:17                 ` Holger, Vodafone
2020-06-15 12:57                   ` Holger, Vodafone
2020-06-16  4:22                   ` Brian Inglis
2020-08-02 20:25                   ` Steinar Bang
2020-08-02 21:00                     ` Eliot Moss
2020-08-04 12:01                       ` Steinar Bang
2020-08-04 13:12                         ` Hamish McIntyre-Bhatty
2020-08-04 16:55                         ` ASSI
2020-06-16  4:59                 ` ASSI
2020-07-02 15:01               ` Steinar Bang
2020-07-02 22:12                 ` Holger, Vodafone
2020-06-16 11:46     ` Holger, Vodafone
2020-06-26  9:15       ` Holger, Vodafone
2020-07-02 14:42         ` Steinar Bang
2020-06-14  6:18 ` Marco Atzeri
2020-06-14 10:38   ` Steinar Bang

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=upzc8sgr6k64.fsf@dod.no \
    --to=sb@dod.no \
    --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).