Gtk-WARNING **: cannot open display
 

Ok, trying out DSL for the first time tonight.... Looks pretty cool so far except I have been stumped already.

I have DSL on client_pc1 and debian on server_pc2.

I boot DSL from cd and open a root shell.

I type "xhost +192.168.0.3" to allow Xapps to connect to the DSL client_pc1

I then "ssh 192.168.0.3 -l my_UID" to connect to server_pc2.

I type "export DISPLAY=192.168.0.2:0" to export my Xapps from the server to the client_pc1.

I type "echo $DISPLAY" and it confirms my Xapps should redirect ok.

I type "gqview &" to launch a test Xapp to the client_pc1 and after about 15 seconds it returns:
(gqview:28926): Gtk-WARNING **: cannot open display:

I also tried "xeyes &" but that returned an error referencing my IP not being allowed. So I went back to the client_pc1 and did "xhost +" to allow any host to connect to the x server.

I've been doing these exact same steps via Knoppix 3.3 as the client_pc1 for a month now but am not familiar enough with DSL to know what's different....

Anyone have any pointers on exporting Xapps onto DSL?

I don't know about small linux particularly, but have you checked out /etc/ssh/sshd_config yet?
You will need a:
X11Forwarding yes
line in order for the ssh daemon to pass data to the X server.

Double check
 

PLease check your disk space using df -h
If partitions like /home /tmp are at a usage above 95% it won't work
Also try removing your host entry from ~/.ssh/known_hosts

Your post is largely irrelevant, and I haven't the heart to keep quiet.

DSL (Da** Small Linux) is a bootable distro (often called a live CD) based on Knoppix. It does not install to the hard drive. It mounts a compressed loopback file on the cd and a ramdisk. Newer versions merge the two, keeping file system changes in the ramdisk. There does not even need to be a hard drive plugged into the system at all. Now if he has no RAM, that's another problem. The odds of that are very slim here though. Reading between the lines, I'd say he had X up and running without problem.

Reason number 2: his post is from July 2004. He certainly does not have the same hd contents he did then (unless the computer has been shelved). This means that any post you submit is not for him, but for anybody else browsing the forum with the same problem.

my two cents