From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Can't open display issue from CMD
Date: Sat, 16 Jan 2021 05:40:59 +0100 [thread overview]
Message-ID: <2c7fc63e-9c18-b90d-348c-40c1401cd273@gmail.com> (raw)
In-Reply-To: <CAKSGAtTA7v47DaHj_k0yQu5bEhUqaub1DXWZ3RLBxnUTyrgBSA@mail.gmail.com>
On 16.01.2021 05:22, Luna Bellofiore via Cygwin wrote:
> All,
>
> I am sending Linux commands from CMD (Windows) through SSH, and I am
> getting "Can't open display". Below I am capturing my issue, the IP number
> is the remote Linux machine.
>
> Microsoft Windows [Version 10.0.19042.746]
> (c) 2020 Microsoft Corporation. All rights reserved.
>
> C:\Users\bellsal>\cygwin\bin\ssh 192.168.0.8 pwd
> /usr/bin/xrdb: Can't open display ''
> /home/bellsal
It seems the remote machine is expecting to run a X interface
by default.
Or you have the startX (or similar) in the personal login scripts
The expect behaviour on a Unix machine (Cygwin or Linux) is:
$ ssh 127.0.0.1 pwd
Marco@127.0.0.1's password:
/home/Marco
> PWD should not require X11 connection, so I don't understand why I am
> getting this issue. Do I need to set an environment variable? If I need
> an xterm from my remote Linux, I know I need to export the display, and
> that works fine. But, I am only sending a simple command from the CMD
> console.
>
> Thanks in advance.
>
> Sa;
I suggest you to check the remote scripts.
It does not seem a Cygwin side problem
Marco
next prev parent reply other threads:[~2021-01-16 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 4:22 Luna Bellofiore
2021-01-16 4:40 ` Marco Atzeri [this message]
[not found] ` <CAEhR91gW6YKbQMoiw+_J3R2AWROcw3N4jOUoyYob1CmGipWsLQ@mail.gmail.com>
2021-01-16 10:48 ` Marco Atzeri
2021-01-16 23:22 ` Hans-Bernhard Bröker
2021-01-17 8:03 ` Sal Bellofiore
2021-01-16 6:15 ` ASSI
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=2c7fc63e-9c18-b90d-348c-40c1401cd273@gmail.com \
--to=marco.atzeri@gmail.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).