Halton Huo wrote:
> On Wed, 2008-05-28 at 11:10 -0700, Karl Dalen wrote:
>> Hi,
>>
>> I've always run Thunderbird remotely by telneting from
>> my Ultra 20 M2 into a local sparc machine and running
>> Thunderbird (sparc) from there using the U-20 as the X display
>> and this has always worked fine. After I installed Nevada build
>> 89 on my U-20 I can no longer run Thunderbird remotely.
>> I get the following error message:
>>
>> "
>> % telnet 192.168.1.100
>> sparc2 > setenv DISPLAY 192.168.1.101:0
>> sparc2 > thunderbird
>> The program 'thunderbird-bin' received an X Window System error.
>> This probably reflects a bug in the program.
>> The error was 'BadWindow (invalid Window parameter)'.
>> (Details: serial 14 error_code 3 request_code 159 minor_code 2)
>> (Note to programmers: normally, X errors are reported asynchronously;
>> that is, you will receive the error a while after causing it.
>> To debug your program, run it with the --sync command line
>> option to change this behavior. You can then get a meaningful
>> backtrace from your debugger if you break on the gdk_x_error() function.)
>> "
>>
>> Don't know if this is a X related problem in the newer X server in
>> Nevada or a thunderbird problem. I get the same error regardless of
>> whether I use 'ssh -X' or telnet (and setting DISPLAY). I have tried an
>> old Thunderbird ver. 1.007 as well as the newest 2.0.0.14 and I get the
>> same error.
>
> Solaris is security by default [1], I suggest you use 'ssh' instead.
Aside from the point he said he used ssh and still had the error, that
error means the connection went through and had problems later - it's
not a connection refused error, it's a "Thunderbird made an illegal
X function call error."
> On your U-20, did you run 'xhost +' before 'ssh -X'?
If you did, then stop that. You should never run xhost +, and certainly
don't need it with ssh.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
