| Re: Unsupported X Windows visual [message #35042 is a reply to message #14303] |
Fri, 09 May 2003 03:29   |
Nigel Wade
Messages: 286 Registered: March 1998
|
Senior Member |
|
|
Karl Schultz wrote:
>
> "Nigel Wade" <nmw@ion.le.ac.uk> wrote in message
> news:b9djf6$j1l$1@south.jnrs.ja.net...
>> Hannah Chenh wrote:
>>
>>> "Karl Schultz" <kschultz_no_spam@rsinc.com> wrote in message
>>>> The thread suggests that there is a patch available that solves a
> problem
>>>
>>> The specified patch(newer version) for solaris 8 was installed on the
>>> blade 100.
>>>
>>>> is not really listing this visual. Perhaps you can post the output
>>>> from
>>>> xdpyinfo? (This will give me some other clues)
>>>
>>> Here is the output of xdpyinfo on the blade:
>>>
>>
>> [dpyinfo snipped]
>>
>> Do you get the same output if you run xdpyinfo on the HP machine?
>> You should if X is really talking to the display on the blade.
>
> The top of the xdpyinfo output suggests that the information is indeed
> from
> the Sun server.
Of course it does - xdpyinfo was run on the Blade.
> The location of the client does not (should not) matter
> as long as the DISPLAY variable points to the server in question.
>
I know that, that was exactly my point. I want to be sure that when logged
onto the HP machine the DISPLAY enviroment variable is pointing correctly
back to the Blade. Providing the output of xdpyinfo *while logged onto the
HP* would demonstrate that, and show what info the X server on the Blade
was providing to clients.
--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : nmw@ion.le.ac.uk
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555
|
|
|
|