Re: No $DISPLAY variable set over ssh

allan wrote on 18/04/2024 13:37: Bug report submitted. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069236 Hi, may I ask how you disabled IPv6 on these machines? Regards, Jörg.

Re: No $DISPLAY variable set over ssh

Hi Allan, On 18/04/24 at 12:38, allan wrote: Have four Sid machines here and ssh -X has worked fine on all of them for years. For the last several days I haven't been able to run graphical applications over ssh from any of these machines. Error says "cannot open display" and if I ssh into the

Re: No $DISPLAY variable set over ssh

Bug report submitted. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069236 On Thu, Apr 18, 2024 at 6:18 AM allan wrote: > > I just fixed it. in /etc/ssh/sshd_config I changed > > #AddressFamily any > > to > > AddressFamily inet > > Reading the host's journal got me pointed in the right

Re: No $DISPLAY variable set over ssh

I just fixed it. in /etc/ssh/sshd_config I changed #AddressFamily any to AddressFamily inet Reading the host's journal got me pointed in the right direction. Thank you for the suggestion :) On Thu, Apr 18, 2024 at 6:10 AM allan wrote: > > > In the context of these SSH sessions, are those

Re: No $DISPLAY variable set over ssh

> In the context of these SSH sessions, are those clients or servers? Both. I've run all four machines as both host and guest when testing. > Do the logs on the host ip.add.re.ss provide any further details? journalctl -t sshd gives this - Apr 18 05:29:03 server sshd[2052]: error: Failed to

Re: No $DISPLAY variable set over ssh

On 18 Apr 2024 05:38 -0500, from wizard10...@gmail.com (allan): > Have four Sid machines here In the context of these SSH sessions, are those clients or servers? > ssh -vv -Y u...@ip.add.re.ss just gives "X11 forwarding request failed > on channel 0" Do the logs on the host ip.add.re.ss

No $DISPLAY variable set over ssh

Have four Sid machines here and ssh -X has worked fine on all of them for years. For the last several days I haven't been able to run graphical applications over ssh from any of these machines. Error says "cannot open display" and if I ssh into the machine $DISPLAY is indeed blank but from a

Re: The DISPLAY variable.

pe...@easthope.ca wrote: > From: deloptes > Date: Wed, 10 Aug 2016 21:12:53 +0200 >> Screen and display are completely different things in different contexts. > > I have one context. A PC with a "Radeon 9600XT 256M V/D/VO" card. > It has one DVI connector and one

Re: The DISPLAY variable.

On Thu, Aug 11, 2016 at 08:14:14AM -0700, pe...@easthope.ca wrote: > > A section in xorg.conf is the only way to create screen 1? Yes. Specifically, you need to set up and allocate monitors for each screen that you want, and you need to turn off Xinerama: Option "Xinerama" "0" in the

Re: The DISPLAY variable.

From: Dutch Ingraham Date: Wed, 10 Aug 2016 14:59:59 -0500 > Yes, xrandr is capable, but you need to spend time with xrandr(1). Specifically, "--screen snum This option selects which screen to manipulate." This parameter allows reference to an extant

Re: The DISPLAY variable.

From: deloptes Date: Wed, 10 Aug 2016 21:12:53 +0200 > Screen and display are completely different things in different contexts. I have one context. A PC with a "Radeon 9600XT 256M V/D/VO" card. It has one DVI connector and one VGA connector. > If you have 1

Re: The DISPLAY variable.

On Wed, Aug 10, 2016 at 11:44:19AM -0700, pe...@easthope.ca wrote: > No luck. The DVI screen is overlaid on the VGA. The display is worse. > I didn't find an error message. Seems that my revised .xsessionrc is > syntactically correct. > > Is xrandr capable of setting the screen numbers as

Re: The DISPLAY variable.

On Wed, Aug 10, 2016 at 11:44:19AM -0700, pe...@easthope.ca wrote: > Thanks Liam and Dan. > > From: Dan Ritter , Wed, 10 Aug 2016 12:12:14 -0400 > > ... if you used XINERAMA or NVidia or AMD's proprietary tools, ... > > Used xrandr commands in .xsessionrc. xrandr controls

Re: The DISPLAY variable.

Thanks Liam and Dan. From: Dan Ritter , Wed, 10 Aug 2016 12:12:14 -0400 > ... if you used XINERAMA or NVidia or AMD's proprietary tools, ... Used xrandr commands in .xsessionrc. peter@dalton:~$ cat .xsessionrc # dalton:/home/peter/.xsessionrc created 2014-12-10. #xrandr

Re: The DISPLAY variable.

pe...@easthope.ca wrote: > xrandr recognizes only one screen?  Why?  Any ideas to have > the two screens recognized according to the documentation? > > Thanks,             ... Peter E. Screen and display are completely different things in different contexts. If you have 1 graphic card you

Re: The DISPLAY variable.

On Wed, Aug 10, 2016 at 07:00:57AM -0700, pe...@easthope.ca wrote: > > Here Debian jessie is running on a machine with two screens > connected to one video card. Therefore try these commands. There are a bunch of ways of doing that. In particular, if you used XINERAMA or NVidia or AMD's

Re: The DISPLAY variable.

pe...@easthope.ca wrote: > Hi, > > https://wiki.debian.org/EnvironmentVariables has no mention > of the DISPLAY variable. > > https://www.debian.org/doc/manuals/debian-reference/ch07.en.html > mentions DISPLAY only incidentally in the last section. > > https://www.

The DISPLAY variable.

Hi, https://wiki.debian.org/EnvironmentVariables has no mention of the DISPLAY variable. https://www.debian.org/doc/manuals/debian-reference/ch07.en.html mentions DISPLAY only incidentally in the last section. https://www.x.org/archive/X11R6.7.0/doc/X.7.html states, "... every X serve

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Wed, 13 Jun 2012 11:24:23 -0700, Rick Thomas wrote: On Jun 13, 2012, at 7:23 AM, Camaleón wrote: Also, while searching for more information on this issue at Google I've found many posts¹, articles and blogs² pointing to a problem with X forwarding and ipv6 though I'm not sure this is

[SOLVED] Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Jun 13, 2012, at 11:24 AM, Rick Thomas wrote: I will file a bug report ASAP against openssh-server. It turns out this is bug #422327, which dates all the way back to 2007, and nothing has been done about it. The bug report even suggested a patch (well, not exactly a patch with

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Jun 12, 2012, at 9:44 PM, Erwan David wrote: On 13/06/12 04:12, Rick Thomas wrote: On Jun 12, 2012, at 1:43 PM, Camaleón wrote: ... mmm, you can compare the ... openssh versions That got me thinking... Looking at a third server (the same i386 Debian Squeeze machine I was using as a

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

, the resulting session had no DISPLAY variable in its env. Moreover, defining DISPLAY=localhost:10.0 ; export DISPLAY did not help. I get xterm Xt error: Can't open display: localhost: 10.0 error-message. That way neither works for me: *** sm01@stt008:~$ ssh sm02@192.168.0.5 (...) sm02@stt005:~$ echo

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Tue, 12 Jun 2012 19:12:42 -0700, Rick Thomas wrote: On Jun 12, 2012, at 1:43 PM, Camaleón wrote: ... mmm, you can compare the ... openssh versions That got me thinking... Looking at a third server (the same i386 Debian Squeeze machine I was using as a client in the previous reply)

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Jun 13, 2012, at 7:23 AM, Camaleón wrote: Also, while searching for more information on this issue at Google I've found many posts¹, articles and blogs² pointing to a problem with X forwarding and ipv6 though I'm not sure this is going to be the case for this but it can be something to

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Jun 13, 2012, at 11:24 AM, Rick Thomas wrote: I will file a bug report ASAP against openssh-server. It turns out this is bug #422327, which dates all the way back to 2007, and nothing has been done about it. The bug report even suggested a patch (well, not exactly a patch with

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Jun 9, 2012, at 3:31 AM, Camaleón wrote: Given that you are login on your own computers you can try with -Y flag (untrusted X11 forwarding) and see how it goes. Another test you can run is by creating a new user and launching slogin -X -vvv macs xterm session from there. Thanks for

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Tue, 12 Jun 2012 01:03:24 -0700, Rick Thomas wrote: On Jun 9, 2012, at 3:31 AM, Camaleón wrote: Given that you are login on your own computers you can try with -Y flag (untrusted X11 forwarding) and see how it goes. Another test you can run is by creating a new user and launching

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

-i386 and Deebian Squeeze armel. Prior to running the recent full-upgrade on the servers, I was able to do slogin -X from any and all of the clients and get an X session with a defined DISPLAY variable in the env (on the servers). I could, for example, start up an xterm on the servers from

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Jun 12, 2012, at 1:43 PM, Camaleón wrote: ... mmm, you can compare the ... openssh versions That got me thinking... Looking at a third server (the same i386 Debian Squeeze machine I was using as a client in the previous reply) I *can* slogin -X and get an X session. On both the

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On 13/06/12 04:12, Rick Thomas wrote: On Jun 12, 2012, at 1:43 PM, Camaleón wrote: ... mmm, you can compare the ... openssh versions That got me thinking... Looking at a third server (the same i386 Debian Squeeze machine I was using as a client in the previous reply) I *can* slogin

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

(e.g. xterm) because there is no DISPLAY variable in the environment. It used to work. I don't know what changed for sure. Does anybody know what can cause this? Try to run slogin with extra verbosity on, e.g.: slogin -X user@server -vvv Thanks for the suggestion. The client is a Mac G5

what causes slogin -X to not generate a $DISPLAY variable on the server?

Recently, when I do slogin -X server (for one particular server, not all of them) the resulting session can't run any X11 utilities (e.g. xterm) because there is no DISPLAY variable in the environment. It used to work. I don't know what changed for sure. Does anybody know what can cause

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Fri, 08 Jun 2012 03:56:35 -0700, Rick Thomas wrote: Recently, when I do slogin -X server (for one particular server, not all of them) the resulting session can't run any X11 utilities (e.g. xterm) because there is no DISPLAY variable in the environment. It used to work. I don't know

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Jun 8, 2012, at 10:06 AM, Camaleón wrote: On Fri, 08 Jun 2012 03:56:35 -0700, Rick Thomas wrote: Recently, when I do slogin -X server (for one particular server, not all of them) the resulting session can't run any X11 utilities (e.g. xterm) because there is no DISPLAY variable

Re: what causes slogin -X to not generate a $DISPLAY variable on the server?

On Jun 8, 2012, at 11:48 AM, Rick Thomas wrote: Here's the output. I see it requesting X11 forwarding (near the end) but I don't see anything specifically saying it was granted. Nor do I see it being specifically refused. Fascinating... FWIW, I tried the same 'slogin -vvv -X' to a

Re: Re: DISPLAY variable not set in ssh session

xauth is need on the server I'm on debian and it's part of the package xbase-clients. cheers! -- This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com http://www.opensubscriber.com/message/debian-user@lists.debian.org/8689320.html -- To UNSUBSCRIBE, email to [EMAIL

Re: Bug#468103: DISPLAY variable not set in ssh session

On Tue, Feb 26, 2008 at 19:40:56 -0500, Rick Thomas wrote: It looks like the xterm package needs to depend on the xauth package -- or at least recommend it. No, this has nothing to do with xterm. openssh-server already suggests xauth (or actually xbase-clients), and documents why in

Re: DISPLAY variable not set in ssh session

. But I can't get X11 forwarding to work. When I use ssh -X or ssh -Y (either option) the connection is made, but the DISPLAY variable is not being set. Anybody know why? No. But using ssh -v might give some clues. One extra potential reason: the target box does not have (the utility) xauth

Re: DISPLAY variable not set in ssh session

the ssh package on it. I can ssh to it just fine. But I can't get X11 forwarding to work. When I use ssh -X or ssh -Y (either option) the connection is made, but the DISPLAY variable is not being set. Anybody know why? No. But using ssh -v might give some clues. One extra potential reason

Re: DISPLAY variable not set in ssh session

On Sat, Mar 01, 2008 at 10:35:51PM -0500, Rick Thomas wrote: No. But using ssh -v might give some clues. One extra potential reason: the target box does not have (the utility) xauth on it. That was it. I did aptitude install xauth and everything was fine. It looks like the xterm

Re: DISPLAY variable not set in ssh session

On 2008-02-26 05:00:13 -0500, Rick Thomas wrote: I just installed Lenny on a G4 Mac. I installed the ssh package on it. I can ssh to it just fine. But I can't get X11 forwarding to work. When I use ssh -X or ssh -Y (either option) the connection is made, but the DISPLAY variable

Re: DISPLAY variable not set in ssh session

, but the DISPLAY variable is not being set. Anybody know why? Make sure X11Forwarding is set to yes in /etc/ssh/sshd_config. -- Kushal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: DISPLAY variable not set in ssh session

) the connection is made, but the DISPLAY variable is not being set. Anybody know why? You need to explicitly enable X11 forwarding on the SSH server side (in /etc/ssh/sshd_config, you should have X11Forwarding yes). Please check that first. On Feb 26, 2008, at 7:16 AM, Kushal Kumaran wrote: Make

Re: DISPLAY variable not set in ssh session

On Tue, Feb 26, 2008 at 05:00:13AM -0500, Rick Thomas wrote: I just installed Lenny on a G4 Mac. I installed the ssh package on it. I can ssh to it just fine. But I can't get X11 forwarding to work. When I use ssh -X or ssh -Y (either option) the connection is made, but the DISPLAY

Re: DISPLAY variable not set in ssh session

-Y (either option) the connection is made, but the DISPLAY variable is not being set. Anybody know why? No. But using ssh -v might give some clues. One extra potential reason: the target box does not have (the utility) xauth on it. That was it. I did aptitude install xauth

Re: DISPLAY variable not set in ssh session

On 2008-02-26 13:52:27 -0500, Rick Thomas wrote: On Feb 26, 2008, at 7:16 AM, Kushal Kumaran wrote: Make sure X11Forwarding is set to yes in /etc/ssh/sshd_config. That's the first thing I checked... Then you can look at the FAQ: /usr/share/doc/openssh-client/faq.html#2.7 But I doubt it

Re: DISPLAY variable not set in ssh session

On 2008-02-26 19:57:50 +, Tzafrir Cohen wrote: No. But using ssh -v might give some clues. One extra potential reason: the target box does not have (the utility) xauth on it. or xauth is not in the default path for ssh (but if the target box is a Debian machine, there should be no

Re: DISPLAY variable not set in ssh session

On 2008-02-26 19:40:56 -0500, Rick Thomas wrote: That was it. I did aptitude install xauth and everything was fine. It looks like the xterm package needs to depend on the xauth package -- or at least recommend it. I don't think so: one can use xterm without xauth (if one doesn't use

Re: DISPLAY-Variable

ausprobiert habe. Normalerweise verwende ich einfach ssh um X-Anwendungen einens entfernten Recherns auf meinem lokalen Rechner zu starten. Hatte das mit der DISPLAY-Variable nur nicht geblickt und deshalb die Frage gestellt. Grüsse, Patrick Wunderlich -- Haeufig gestellte Fragen und Antworten (FAQ

DISPLAY-Variable und Sound (was DISPLAY-Variable)

Btw, ich habe mich neulich vom Laptop auf den Desktop per SSH eingeloggt. Dann habe ich die DISPLAY-Variable auf ':0' gesetzt und den mplayer gestartet, er ist dann auch auf dem Bildschirm des Desktops erschienen und hat den Film gespielt. Aber ich hatte keinen Sound. Liegt das am speziellen

Re: DISPLAY-Variable und Sound (was DISPLAY-Variable)

On 02.Mär 2005 - 10:44:12, Moritz Karbach wrote: Btw, ich habe mich neulich vom Laptop auf den Desktop per SSH eingeloggt. Dann habe ich die DISPLAY-Variable auf ':0' gesetzt und den mplayer gestartet, er ist dann auch auf dem Bildschirm des Desktops erschienen und hat den Film

Re: DISPLAY-Variable und Sound (was DISPLAY-Variable)

Der Sound ist unabhaengig von X11, wenn du Sound auch auf andere Rechner umleiten willst, musst du einen Sounddaemon wie esd oder artsd nutzen und diesem das sagen... Anders wird das nix... Gut, dann war wohl was anderes falsch. Ja, die Anlage war an :-) Dank dir, - Moritz -- Haeufig

Re: DISPLAY-Variable

On Tue, Mar 01, 2005 at 10:52:06PM +0100, Patrick Wunderlich wrote: in der Konsole unter X ist die DISPLAY-Variable standardmäßig auf :0 gesetzt. Wenn ich DISPLAY auf localhost:0 setze, dürfte das doch eigentlich genauso funktionieren, oder? Noe, im ersten Fall kann die Kommunikation ueber

Re: DISPLAY-Variable

Patrick Wunderlich [EMAIL PROTECTED] (Di 01 Mär 2005 22:52:06 GMT): Ich bekomme dann jedoch beim Starten von xterm folgende Fehlermeldung: xterm Xt error: Can't open display: localhost:0 localhost - dann will der Client mit dem XServer über TCP/IP reden (also geht der davon aus, dass Du auf

Re: DISPLAY-Variable

On 2005-03-01 22:52:06 +0100, Patrick Wunderlich wrote: Hallo Debian Fans, in der Konsole unter X ist die DISPLAY-Variable standardmäßig auf :0 gesetzt. Wenn ich DISPLAY auf localhost:0 setze, dürfte das doch eigentlich genauso funktionieren, oder? Nicht direkt. Wenn ich mich nicht täusche

Re: DISPLAY-Variable in Woody

Martin Rebenstorff [EMAIL PROTECTED] wrote: ich habe folgendes Problem. Seit ich auf woody umgestellt habe, spielt meine DISPLAY Variable, bzw. mein XServer (4.1.0-16) verrückt. Nur wenn ich die DISPLAY Variable auf :0 (oder :0.0) setze kann ich X-Applikationen starten. Setzte ich DISPLAY auf

Q: Setting the environment display variable??

Hi, Trying to install Words, I got: ./setup Initializings installation. Please wait... Before running this product, you must set your environment DISPLAY variable. Read up in the FAQ and Running Linux and no mention is made of a display variable... It has to be a basic shell configuration item

RE: Q: Setting the environment display variable??

On 07-Nov-2000 Jonathan Gift wrote: Hi, Trying to install Words, I got: ./setup Initializings installation. Please wait... Before running this product, you must set your environment DISPLAY variable. Read up in the FAQ and Running Linux and no mention is made of a display variable