| Re: Unsupported X Windows visual [message #35046 is a reply to message #14303] |
Thu, 08 May 2003 17:18   |
Karl Schultz
Messages: 341
Registered: October 1999
|
Senior Member |
|
|
"Hannah Chenh" <hchenh@ucsd.edu> wrote in message
news:ca36e435.0305081429.57cea684@posting.google.com...
>> Hannah, what DEVICE commands are being issued? (Make sure that you
check
>> startup files, etc)
>
> Here are the steps I used:
>
> 1. From SUN Blade terminal, login HP via SSH (IDL was installed on HP)
> 2. set DISPLAY to SUN's display
> 3. issue "xhost +" on SUN's terminal
> 4. start IDL
> 5. IDL> DEVICE,PSEUDO_COLOR=8
> 6. IDL> DEVICE,GET_VISUAL_DEPTH=DEPTH;PRINT,DEPTH
> % Unsupported X Windows visual (class: PseudoColor, depth: 8).
> Substituting default (class: TrueColor, Depth: 24).
> IDL>
>
> I got the same error if I use IDL_STARTUP file.
I sat down at the console of a Sun workstation and ran the same IDL
commands. The X server had several visuals, including a 24-bit TrueColor
and an 8-bit PseudoColor. The latter was the default visual on the X
server. So, the environment is pretty similar to the one on your Blade.
I didn't get the error message and the value of depth was 8, as expected.
I then started a new IDL session and just ran the DEVICE,
GET_VISUAL_DEPTH=depth command and got a value of 24 for depth.
So, things look OK on this machine. There may be something wrong with the X
server on your Blade machine. IDL is just calling XGetVisualInfo with the
Screen, Class, and Depth set in the template, and is getting no visuals in
the returned list. This seems broken to me.
There is only one Screen on your server, so I don't think it is
Screen-related.
I don't think that SSH is the problem, because you wouldn't have gotten a
Display connection if there was an SSH tunneling problem.
This code hasn't changed much in IDL over many releases, so I doubt that you
have something old enough that may have had a problem in this area.
If you are a programmer, it wouldn't be hard to write a short program that
opens an X connection and just calls XGetVisualInfo with the template set as
I mentioned above. If the list comes back empty, then you'd have something
concrete to report to Sun.
My last longshot suggestion is to try running IDL in 32-bit mode on the HP,
if you were trying it in 64-bit mode. You are sending X protocol over the
network, and there's a chance that there's a protocol encode/decode problem
someplace.
Karl
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
