Error: Can't open display: 199.63.246.193:0.0
 

Hi,
I'm trying to run an UI based application installed on a Solaris m/c by connecting remotley from Windows, I get the error "Can't open Display".
Also made sure that DISPLAY environment variable is set by doing
"export DISPLAY=x.x.x.x:0.0" but this doesn't solve the problem. What setting I need to make to get this working?


Thanks for your help in adv

Regards,
Hussain

X-forward using ssh. If your using SSH to remote into solaris, your ssh client from your home machine has to have X forwarding through SSH enabled.

Check your firewall to see if its not block the port your UI app is using.

Solaris m/c has Sshillix 0.7.2 installed on it

I have a XMINS installed in my windows m/c, I tried to access the Solaris machine by launching the XMINS application( I did set the DISPLAY environment variable "export DISPLAY=199.63.246.193:0.0" from Putty before starting XMINS). XMINs asks for the IP address, I enter the IP of my Solaris m/c, but after that it doesn't ask for username/pwd. Is there anything I need to configure on Sol m/c to enable access from XMINS?

Also I'm not sure if XMINS works with Schillix? Do I need to install another X11 server to access the Solaris m/c remotely

Best regards,
Hussain

Check to see if the Solaris machine is configure to serve an X window. I think the process name for it I recall was XDM for Solaris.

Does your Windows host actually have an X server running? It sounds like you may be experiencing the usual X-newbie confusion of where the X server and clients are, and what mechanism is used to connect the two. To make sure we are talking about the same thing, I will rephrase your question.
You have a Windows host, where you want the graphical content and control to be displayed, and the application creating the GUI is running on a remote Solaris host.
In this scenario, the GUI application that runs on Solaris is the X client, and the X server will need to run on the Windows host. The $DISPLAY variable on the Solaris host tells all X GUI applications how to find the X server to which they are to connect. Moreover, the X server identified by $DISPLAY must actually exist and be accessible to the client. What X server is running on your Windows host? The value of $DISPLAY can be manually configured to point at the X server on your Windows host (or any other X server, for that matter). However, if you use an ssh client to connect & login to the Solaris host, that client can be told to create a tunnel for X traffic back to the X server. In doing so, the X tunnel will set up $DISPLAY to be something like 'localhost:12' ('localhost', plus some low-ish integer server instance). The ssh connection will receive all of the connections to the value specified in $DISPLAY, and silently relay them back to the X server at the ssh client host.
Configuration of the X tunnel will be ssh-client specific. You seem to be using Putty. Perhaps someone acquainted with that tool can describe how to set up the tunnel.

--- rod.

Use mobaterm in windows.

The send to ip:0 not :0.0

I think that is it.

Hi,

I am unable to set LD_LIBRARY_PATH from the Graphical view ( after running startx command).
LD_LIBRARY_PATH is an environmental variable.
Please help me to resove this issue.

Thanks in advance.

Hi,

Here below is the output of startx command on console mode. May be this will helpful to you to understand the problem deeply.
By default $DISPLAY is not set.




X Window System Version 6.9.0

Release Date: 21 December 2005

X Protocol Version 11, Revision 0, Release 6.9

Build Operating System: SunOS 5.10 Generic i86pc

Current Operating System: SunOS unknown 5.11 schily147i i86pc

Build Date: 27 February 2006

Before reporting problems, check http://wiki.X.Org

to make sure that you have the latest version.

Module Loader present

Markers: (--) probed, (**) from config file, (==) default setting,

(++) from command line, (!!) notice, (II) informational,

(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 8 19:42:48 2011

(EE) Unable to locate/open config file

ads@unknown:~/ads/bftest/ads-drs-9-20101130-104123/folge$ xf86AutoConfig: Primary PCI is 0:2:0

Running "/usr/X11R6/bin/getconfig -X 60900000 -I /etc/X11,/usr/X11R6/etc/X11,/usr/X11R6/lib/modules,/usr/X11R6/lib/X11/getconfig -v 0x8086 -d 0x2582 -r 0x04 -s 0x1028 -b 0x0179 -c 0x0300"

getconfig.pl: Version 1.0.

getconfig.pl: Xorg Version: 6.9.0.0.

getconfig.pl: 23 built-in rules.

getconfig.pl: rules file '/usr/X11R6/lib/X11/getconfig/xorg.cfg' has version 1.0.

getconfig.pl: 1 rule added from file '/usr/X11R6/lib/X11/getconfig/xorg.cfg'.

getconfig.pl: Evaluated 24 rules with 0 errors.

getconfig.pl: Weight of result is 500.

New driver is "i810"

(==) Using default built-in configuration (53 lines)

(EE) Failed to load module "fbdev" (module does not exist, 0)

(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found

The XKEYBOARD keymap compiler (xkbcomp) reports:

> Error: Mode_switch added to symbol map for multiple modifiers

> Using Mod3, ignoring Mod2.

Errors from xkbcomp are not fatal to the X server

Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!

You are confused about the use of X. Please read this and my previous post in this thread closely.
You do not need to start the X server on the Solaris host. You say you have XMins installed on your Windows host. Installed, but is it running? If not, you need to start it there. The X server runs on the host hardware where you want to see the graphical output and where you have a keyboard and pointer (mouse). The applications that use the X server (X clients) can run anywhere. The mechanism that allows the X clients to attach to the X server (XMins) is described in my prior post.
An easy-to-try X client that is almost certain to exist on all Solaris hosts is xterm. You start by starting the X server (Xmins) on the Windows host (I can't help you there; perhaps try startx). Next, you log into the Solaris host from your Windows host. Since you seem to have Cygwin installed there, I will assume you can use the Cygwin ssh client, and use the -X option (from a Windows cygwin shell):
Now, having set up the X tunnel with the -X option, you can verify that the $DISPLAY variable is set in the Solaris shell.
The numeric part following the colon can be any low integer number. The part following the '.' will almost always be '0'.
Assuming everything is good to this point, run an X client from the Solaris shell:
A window should pop up, with a shell commandline ready to accept input. If this happens, your X server and connections to it are all good, and you should be able to run any X applications on the Solaris host.

$LD_LIBRARY_PATH on the X client host has nothing to do with the use of X per se. It may or may not be required to run your application, but it doesn't have any particular connection to the use of X. The $DISPLAY variable must be set in the X client host in order to use X applications.

EDIT: looks like there are various ways to start Cygwin/X

--- rod.

Hi theNbomr.

Thank you for your kind help. We becomes able to fix this issue.
Now we can watch the graphical view from windows machine.

If you don't mind i want to take your little help.
When i am running my project from my windows machine using xming in xterm window it produce the correct output. Basically output is a graphical image having differerent colours.

But when i am tring this from the opensolaris based distro machine ( first startx and then xterm window to execute project) i am getting a error and output is not able to display.

Message is:

warning: cannot convert string "<key> Escape,_key_cancel" to type virtual binding
(11030.132521) winpic_new : not a color screen with 8/24 bit planes(16).

Please give some suggestion.

X servers have various modes of operation, called visuals, which are groupings of optional functionality. These include, especially, the depth of color supported by a particular mode. Color depth is defined in X as a number of bits that define the color of each particular pixel. It looks like the particular visual required by your X client application is not supported by that X server. You may be able to reduce the requirements of your application (by modifying the code and rebuilding it appropriately), but it is likely that the limitation of the X server is based on physical limitations of the video hardware on which the X server is running.
With respect to the warning regarding the key bindings, it appears that the application has tried to create a key binding that causes a specific key-code to emit a special string, but for some reason the X server is unable to accomplish this. This, too, may be a limitation of the X server, perhaps because the specified key does not exist on the server's keyboard.

--- rod.