|
Replies:
12
-
Last Post:
May 31, 2008 8:42 PM
by: karl_d
|
|
|
Posts:
54
From:
Sunnyvale
Registered:
10/8/07
|
|
|
|
Problem in running thunderbird remotely
Posted:
May 28, 2008 11:10 AM
To: Communities » desktop » discuss
|
|
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.
On my earlier OS on the same U-20 (Solaris 10, 11/06)
I did not have this problem. Logging in from a Linux machine to
the Sparc machine does not give this thunderbird error.
Any help would be appreciated.
/Karl D
|
|
|
Posts:
533
From:
CN
Registered:
8/11/05
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 29, 2008 6:41 AM
in response to: karl_d
|
|
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.
On your U-20, did you run 'xhost +' before 'ssh -X'?
[1] http://opensolaris.org/os/community/security/projects/sbd/
-Halton.
>
> On my earlier OS on the same U-20 (Solaris 10, 11/06)
> I did not have this problem. Logging in from a Linux machine to
> the Sparc machine does not give this thunderbird error.
>
> Any help would be appreciated.
>
> /Karl D
>
>
> This message posted from opensolaris.org
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris dot org
_______________________________________________
desktop-discuss mailing list
desktop-discuss at opensolaris dot org
|
|
|
|
|
Posts:
5,504
From:
US
Registered:
3/9/05
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 29, 2008 8:14 AM
in response to: halton
|
|
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 dot coopersmith at sun dot com
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
desktop-discuss mailing list
desktop-discuss at opensolaris dot org
|
|
|
|
|
Bob Friesenhahn
bfriesen@simple.dall...
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 29, 2008 8:50 AM
in response to: halton
|
|
On Thu, 29 May 2008, Halton Huo wrote:
>
> Solaris is security by default [1], I suggest you use 'ssh' instead.
> On your U-20, did you run 'xhost +' before 'ssh -X'?
Using 'xhost +' is completely the opposite of security since it
basically says to disable all security and let anyone use my display
(including that xterm left logged in as root). What is the point of
using ssh at all if you use 'xhost +'? You might as well be using rsh
and rlogin as well or perhaps just post your username and password in
your blog. ;-)
Speaking of SSH, it seems that the latest Solaris 10 patch for SSH
have broken 'ssh -X'. There is apparently a local hijack exploit
related to 'ssh -X'. After remote login with 'ssh -X', DISPLAY is not
set on the remote Solaris 10 system even though the remote system has
'X11Forwarding yes' in /etc/ssh/sshd_config.
Bob
======================================
Bob Friesenhahn
bfriesen at simple dot dallas dot tx dot us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
desktop-discuss mailing list
desktop-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,032
From:
US
Registered:
3/24/06
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 29, 2008 9:00 AM
in response to: Bob Friesenhahn
|
|
Hi Bob. I tried on a fresh install of U5 and it works, or is the patch for U5 cause I see quite a few from smpatch.
James On May 29, 2008, at 10:50 AM, Bob Friesenhahn wrote: On Thu, 29 May 2008, Halton Huo wrote:
Solaris is security by default [1], I suggest you use 'ssh' instead.
On your U-20, did you run 'xhost +' before 'ssh -X'?
Using 'xhost +' is completely the opposite of security since it basically says to disable all security and let anyone use my display (including that xterm left logged in as root). What is the point of using ssh at all if you use 'xhost +'? You might as well be using rsh and rlogin as well or perhaps just post your username and password in your blog. ;-) Speaking of SSH, it seems that the latest Solaris 10 patch for SSH have broken 'ssh -X'. There is apparently a local hijack exploit related to 'ssh -X'. After remote login with 'ssh -X', DISPLAY is not set on the remote Solaris 10 system even though the remote system has 'X11Forwarding yes' in /etc/ssh/sshd_config. Bob ====================================== B ob Friesenhahn bfriesen at simple dot dallas dot tx dot us, http://www.simplesystems.org/users/bfriesen/GraphicsMagick Maintainer, http://www.GraphicsMagick.org/_______________________________________________ desktop-discuss mailing list desktop-discuss at opensolaris dot org
|
|
|
|
|
Bob Friesenhahn
bfriesen@simple.dall...
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 29, 2008 9:13 AM
in response to: sparcdr
|
|
On Thu, 29 May 2008, James Cornell wrote:
> Hi Bob. I tried on a fresh install of U5 and it works, or is the patch for
> U5 cause I see quite a few from smpatch.
I am still running U4 here, but this would be a patch to U5 since it
is recent (May/22/2008). The x86 patch ID is 126134-03 and the SPARC
patch ID is 126133.
Problem Description:
6504798 ssh fails for users when ngroups_max=32
6684003 fix CVE-2008-1483 in SunSSH
(from 126134-02)
"This patch revision accumulates generic patch 127715-03 into Solaris
Update S10U5 release.
Here is a link to a description of CVE-2008-1483:
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-1483
Nowhere does the patch description say that it entirely disables 'ssh
-X' but that seems to be the case. The client requests the X11
session and the server silently ignores it.
Bob
======================================
Bob Friesenhahn
bfriesen at simple dot dallas dot tx dot us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
desktop-discuss mailing list
desktop-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,032
From:
US
Registered:
3/24/06
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 29, 2008 9:15 AM
in response to: Bob Friesenhahn
|
|
I ran updatemanager over x11 using ssh -x just yesterday with it...
James On May 29, 2008, at 11:13 AM, Bob Friesenhahn wrote: On Thu, 29 May 2008, James Cornell wrote: Hi Bob. I tried on a fresh install of U5 and it works, or is the patch for U5 cause I see quite a few from smpatch.
I am still running U4 here, but this would be a patch to U5 since it is recent (May/22/2008). The x86 patch ID is 126134-03 and the SPARC patch ID is 126133. Problem Description: 6504798 ssh fails for users when ngroups_max=32 6684003 fix CVE-2008-1483 in SunSSH (from 126134-02) "This patch revision accumulates generic patch 127715-03 into Solaris Update S10U5 release. Here is a link to a description of CVE-2008-1483: http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-1483Nowhere does the patch description say that it entirely disables 'ssh -X' but that seems to be the case. The client requests the X11 session and the server silently ignores it. Bob ====================================== Bob Friesenhahn bfriesen at simple dot dallas dot tx dot us, http://www.simplesystems.org/users/bfriesen/GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
|
|
|
|
|
Bob Friesenhahn
bfriesen@simple.dall...
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 29, 2008 9:29 AM
in response to: sparcdr
|
|
On Thu, 29 May 2008, James Cornell wrote:
> I ran updatemanager over x11 using ssh -x just yesterday with it...
Good for you.
>From one Solaris 10U4 system (x86) to another Solaris 10U4 system
(SPARC) with both of them updated with the latest SSH patch, this
error is reported on the server side in /var/adm/messages:
[ID 800047 auth.error] error: Failed to allocate internet-domain X11 display socket.
This is surely the wrong forum for this discussion, but if people here
find that 'ssh -X' stops working, this latest SSH patch is likely the
cause.
Bob
======================================
Bob Friesenhahn
bfriesen at simple dot dallas dot tx dot us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
desktop-discuss mailing list
desktop-discuss at opensolaris dot org
|
|
|
|
|
Posts:
5,504
From:
US
Registered:
3/9/05
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 29, 2008 8:15 AM
in response to: karl_d
|
|
Karl Dalen wrote:
> (Details: serial 14 error_code 3 request_code 159 minor_code 2)
*sigh* I really need to find the genius who decided GTK needed to
remove useful information from X errors and make them impossible to
debug.
That is an error from an X extension call, but GTK has thrown away
the information about which one, and since the codes are dynamically
assigned based on your server configuration, we can't tell from here.
To debug this further, a developer will also need you to run:
xdpyinfo -queryExt | grep "opcode: 159"
so that we can know what request code 159 is assigned to in your
server configuration.
--
-Alan Coopersmith- alan dot coopersmith at sun dot com
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
desktop-discuss mailing list
desktop-discuss at opensolaris dot org
|
|
|
|
|
Posts:
54
From:
Sunnyvale
Registered:
10/8/07
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 31, 2008 8:42 PM
in response to: alanc
To: Communities » desktop » discuss
|
|
> Karl Dalen wrote:
> > (Details: serial 14 error_code 3 request_code 159
> minor_code 2)
>
> That is an error from an X extension call, but GTK
> has thrown away
> the information about which one, and since the codes
> are dynamically
> assigned based on your server configuration, we can't
> tell from here.
Thanks for your replies.
I just found that indeed this is a generic gtk problem. Any gtk application
I run remotely from nv fails with the same error:
% gtk-demo
The program 'gtk-demo' 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.
:
Notice that running locally works fine and also if I log
in to sparc2 from a Linux machine (running Xorg ver. 7.1.1)
there is no gtk error. Could it be that the newer X server
in nv in some way picks up on something. It did work in Solaris 10.
Also, if I log into the Linux machine gtk works so
obviously it's a problem with gtk-X interface in communication
between Solaris 10 and Nevada.
>
> To debug this further, a developer will also need you
> to run:
> xdpyinfo -queryExt | grep "opcode: 159"
> so that we can know what request code 159 is assigned
> to in your
> server configuration.
% xdpyinfo -queryExt | grep "opcode: 159"
XINERAMA (opcode: 159)
/Karl
|
|
|
|
|
Posts:
392
From:
SG
Registered:
9/15/06
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 29, 2008 7:19 PM
in response to: karl_d
|
|
Hi Karl,
Just curious whether this problem only exists for Thunderbird? How about
launching a Firefox remotely, or some other applications?
-Alfred
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.
>
> On my earlier OS on the same U-20 (Solaris 10, 11/06)
> I did not have this problem. Logging in from a Linux machine to
> the Sparc machine does not give this thunderbird error.
>
> Any help would be appreciated.
>
> /Karl D
>
>
> This message posted from opensolaris.org
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris dot org
>
_______________________________________________
desktop-discuss mailing list
desktop-discuss at opensolaris dot org
|
|
|
|
|
Posts:
8
From:
Registered:
5/23/07
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 31, 2008 11:34 AM
in response to: alfred
To: Communities » desktop » discuss
|
|
It appears as though sshd X11 forwarding on S10u5 is broken. For some reason, when it tries listening for connections on IPv6, any attempt to connect from a client (even an IPv4 client) with the -X (X11 forwarding) option results in the error message "error: Failed to allocate internet-domain X11 display socket." being written to the console. And indeed, DISPLAY is not set as expected in the login shell.
The work-around is to force sshd to run in IPv4-only mode.
According to the comments in sshd_config, that should be doable by changing the ListenAddress line:
# IPv4 only
ListenAddress 0.0.0.0
# IPv4 & IPv6
#ListenAddress ::
However, making this change did not fix the problem for me. I had to force IPv4-only mode by supplying the -4 option when starting sshd. I looked in SMF to see if I could do that by setting a service property, but it appears that it is not possible. Thus, I resorted to a hack of the svc script that starts sshd (/lib/svc/method/sshd):
# SMF arguments (start and restart [really "refresh"])
'start')
/usr/lib/ssh/sshd -4
;;
(I added the "-4").
Then do a "svcadm restart svc:/network/ssh:default" to put this change into effect, logout and ssh -X back in, and X11 forwarding starts working again.
If someone has a better solution to this problem, I'd love to hear it.
Thanks,
Bill
|
|
|
|
|
Bob Friesenhahn
bfriesen@simple.dall...
|
|
|
|
Re: Problem in running thunderbird remotely
Posted:
May 31, 2008 1:33 PM
in response to: korb
|
|
On Sat, 31 May 2008, Bill Korb wrote:
>
> If someone has a better solution to this problem, I'd love to hear it.
This bug was added to my Solaris 10 systems via the most recent SSH
patch so it seems that the best solution is for Sun to release yet
another patch to fix what they broke.
Bob
======================================
Bob Friesenhahn
bfriesen at simple dot dallas dot tx dot us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
desktop-discuss mailing list
desktop-discuss at opensolaris dot org
|
|
|
|
|
