Re: Problem connecting app to X display server
On Mon, Jun 24, 2002 at 05:19:43PM -0600, Sivea Key wrote: > HI, > I'm new to Debian and LINUX so any help would be greatly appreciated. > > I am trying to run a simulation program on Debian. It compiles fine (now) but > whenever I try to launch the gui it tells me it can't connect to the display > and that I need to run: export DISPLAY=:0 [or setenv--I'm in BASH > so I use export] > > Running that command produces no error but also doesn't help. I have tried > using the machine name and also tried using what appeared to be the display > server name. I am not certain I used the actual display server name--where > exactly do I find it and what should it look like? (I used defaults on > everything except the computer name during install and again during > reconfiguration.) > > Thanks again for any help offered, > Sivea You could try localhost:0 Also, are you running the program as the same user as your X session? Is this a local program or are you logging into another machine to start this prog? Try entering the FQDN as your DISPLAY and xhost the remote machine's FQDN. Even if this is a local program, you may have a DNS problem, check /etc/hosts and /etc/resolv.conf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem connecting app to X display server--more failed efforts
Vineet wrote: " > Now, how do I set the DISPLAY (and other variables I had to set for this > program) permanently? And do I set them as root, su, or my normal user > account? Put them in your ~/.bashrc . Although this will make the apps display on the other machine even when you're sitting at the one! You could instead put an alias in your .bashrc that sets it up for you, something like alias otherhost='export DISPLAY=otherhost:0' " I think I need to understand a bit more about what you are suggesting. The Debian Unleashed book mentioned something about ~/.login or ~./profile but I haven't found any more details yet as to the ramifications. To be clearer, I am not actually connecting remotely to the X display server. I am simply connecting a local app to it but had an error instructing me to type "export DISPLAY=:0" before trying again. As we know, that didn't work but your suggestion did, Vineet. The app I'm trying to get running is a military simulation app called OneSAF which is huge, complex and somewhat cobbled together. So far, I haven't been able to get it to launch completely. Unfortunately, I am new to the app as well as Linux. I just happened to be a willing mind and a warm body at the right time for the right price. :} There are about 4 variables that must be set before starting the app as well as the "fixjava" executable (which must be run before each restart of the app). I have 2 user accounts as well as root that are used with this app and I would like the variables to be set for all of them--globally(?). It would be handy to tie the fixjava "program" to the launch command, too. BTW, The software involved is Deb 2.2, JDK 1.1.7, JFC 1.1, Swing 1.1.1, TCL/TK 8.3.4, Jikes 1.02-1 and OpenMotif 2.1.3. I used the G++ compiler to compile it. In case that gives a clue. A *NIX cohort suggested that perhaps I am not connecting to X Windows properly since I have had that DISPLAY error (still having trouble on another machine) and now an error "Could not create the registry: java.net.SocketException: No such device" and the launch hangs there. Ideas? I am also trying to connect with the OneSAF list. It's government, takes time and is complicated. I will be working on a vi tutorial while I await further instructions. ;) Thanks, guys! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem connecting app to X display server--more failed efforts
* Sivea Key ([EMAIL PROTECTED]) [020625 11:42]: > Now, how do I set the DISPLAY (and other variables I had to set for this > program) permanently? And do I set them as root, su, or my normal user > account? Put them in your ~/.bashrc . Although this will make the apps display on the other machine even when you're sitting at the one! You could instead put an alias in your .bashrc that sets it up for you, something like alias otherhost='export DISPLAY=otherhost:0' good times, Vineet -- http://www.doorstop.net/ -- "Computer Science is no more about computers than astronomy is about telescopes." -E.W. Dijkstra pgpLHs9lJTppb.pgp Description: PGP signature
Re: Problem connecting app to X display server--more failed efforts
>- Original Message - >From: "Vineet Kumar" <[EMAIL PROTECTED]> >To: >Sent: Tuesday, June 25, 2002 11:04 AM >Subject: Re: Problem connecting app to X display server--more failed efforts >* Sivea Key ([EMAIL PROTECTED]) [020625 09:45]: >> [additional efforts] >> I did some further research and typed: set DISPLAY :0.0; export >> DISPLAY >That looks like a mixture of csh-style and sh-style syntax. try isntead >DISPLAY=:0 >export DISPLAY This syntax (with the addition of the hostname before the :0, worked great!!). The orginal syntax is directly from "Debian GNU/Linux 2.1 Unleashed". Hmm. >That's the matter of syntax. As for the matter of semantics, you >shouldn't be resetting DISPLAY to use X apps across a network. You >should be using ssh with X11 forwarding. The reason is that sending an X >connection in the clear is like using telnet: anything you type can be >sniffed from the network. ssh helps protect you from that by tunneling >the connection through an encrypted tunnel. Debian helps you stay secure >by not enabling tcp listening by default in the X server installation. >The best way to do this is to start on the machine you want the app to >be displayed on, and go >ssh -X otherhost application >For this to work, the ssh server on otherhost must allow X11Forwarding >in /etc/ssh/sshd_config as well. Thanks for the advice, I had just read similar precautions in the aforementioned book. I am, however, on a test machine within a private production LAN trying to get a distributed app style simulation software to run so I can help alter it to a client's specs. I want to keep everything as vanilla as possible so I have less to troubleshoot! :) Now, how do I set the DISPLAY (and other variables I had to set for this program) permanently? And do I set them as root, su, or my normal user account? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem connecting app to X display server--more failed efforts
* Sivea Key ([EMAIL PROTECTED]) [020625 09:45]: > [additional efforts] > I did some further research and typed: set DISPLAY :0.0; export > DISPLAY That looks like a mixture of csh-style and sh-style syntax. try isntead DISPLAY=:0 export DISPLAY That's the matter of syntax. As for the matter of semantics, you shouldn't be resetting DISPLAY to use X apps across a network. You should be using ssh with X11 forwarding. The reason is that sending an X connection in the clear is like using telnet: anything you type can be sniffed from the network. ssh helps protect you from that by tunneling the connection through an encrypted tunnel. Debian helps you stay secure by not enabling tcp listening by default in the X server installation. The best way to do this is to start on the machine you want the app to be displayed on, and go ssh -X otherhost application For this to work, the ssh server on otherhost must allow X11Forwarding in /etc/ssh/sshd_config as well. good times, Vineet -- http://www.doorstop.net/ -- "I disapprove of what you say, but I will defend to the death your right to say it." --Beatrice Hall, The Friends of Voltaire, 1906 pgpOjpENDpKax.pgp Description: PGP signature
RE: Problem connecting app to X display server--more failed efforts
> On 24-Jun-2002 Sivea Key wrote: > > I'm new to Debian and LINUX so any help would be greatly appreciated. > > > > I am trying to run a simulation program on Debian. It compiles fine (now) but > > whenever I try to launch the gui it tells me it can't connect to the display > > and that I need to run: export DISPLAY=:0 [or setenv--I'm in BASH > > so I use export] > > > > Running that command produces no error but also doesn't help. I have tried > > using the machine name and also tried using what appeared to be the display > > server name. I am not certain I used the actual display server name--where > > exactly do I find it and what should it look like? (I used defaults on > > everything except the computer name during install and again during > > reconfiguration.) > > > > I haven't yet discovered what man page to specify for more information, none > > of the 4 books I have nor the Xfree86 or Debian site have revealed anything > > useful as yet. Admitedly, I may be asking the wrong questions. > > > > In the X session where you want to see the window open a terminal program and > type: echo $DISPLAY. Whatever you see as output is what you need to export at > the console. I ran echo $DISPLAY and it returned nothing. I checked "set" and found no DISPLAY configuration parameter listed at all. When I installed Debian 2.2, I distinctly chose settings. Furthermore, X windows starts. What am I missing and what do I need to do? Or where should I look for help? [additional efforts] I did some further research and typed: set DISPLAY :0.0; export DISPLAY where was the hostname of my Deb box--debian2. Yet when I ran echo $DISPLAY again, I still got nothing and no DISPLAY setting shows when I type: set. Help. Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem connecting app to X display server
- Original Message - From: "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> To: "Sivea Key" <[EMAIL PROTECTED]> Cc: Sent: Monday, June 24, 2002 5:27 PM Subject: RE: Problem connecting app to X display server > > On 24-Jun-2002 Sivea Key wrote: > > HI, > > I'm new to Debian and LINUX so any help would be greatly appreciated. > > > > I am trying to run a simulation program on Debian. It compiles fine (now) but > > whenever I try to launch the gui it tells me it can't connect to the display > > and that I need to run: export DISPLAY=:0 [or setenv--I'm in BASH > > so I use export] > > > > Running that command produces no error but also doesn't help. I have tried > > using the machine name and also tried using what appeared to be the display > > server name. I am not certain I used the actual display server name--where > > exactly do I find it and what should it look like? (I used defaults on > > everything except the computer name during install and again during > > reconfiguration.) > > > > I haven't yet discovered what man page to specify for more information, none > > of the 4 books I have nor the Xfree86 or Debian site have revealed anything > > useful as yet. Admitedly, I may be asking the wrong questions. > > > > In the X session where you want to see the window open a terminal program and > type: echo $DISPLAY. Whatever you see as output is what you need to export at > the console. I ran echo $DISPLAY and it returned nothing. I checked "set" and found no DISPLAY configuration parameter listed at all. When I installed Debian 2.2, I distinctly chose settings. Furthermore, X windows starts. What am I missing and what do I need to do? Or where should I look for help? Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Problem connecting app to X display server
On 24-Jun-2002 Sivea Key wrote: > HI, > I'm new to Debian and LINUX so any help would be greatly appreciated. > > I am trying to run a simulation program on Debian. It compiles fine (now) but > whenever I try to launch the gui it tells me it can't connect to the display > and that I need to run: export DISPLAY=:0 [or setenv--I'm in BASH > so I use export] > > Running that command produces no error but also doesn't help. I have tried > using the machine name and also tried using what appeared to be the display > server name. I am not certain I used the actual display server name--where > exactly do I find it and what should it look like? (I used defaults on > everything except the computer name during install and again during > reconfiguration.) > > I haven't yet discovered what man page to specify for more information, none > of the 4 books I have nor the Xfree86 or Debian site have revealed anything > useful as yet. Admitedly, I may be asking the wrong questions. > In the X session where you want to see the window open a terminal program and type: echo $DISPLAY. Whatever you see as output is what you need to export at the console. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
