Bug 832

Summary:

X forwarding crashes on some applications

Product:

Portable OpenSSH

Reporter:

Kevin Taylor <ktaylor>

Component:

ssh

Assignee:

OpenSSH Bugzilla mailing list <openssh-bugs>

Status:

CLOSED WORKSFORME

Severity:

normal

Priority:

Version:

3.8p1

Hardware:

ix86

OS:

Linux

Attachments:

Description	Flags
verbose output (X related stuff)	none

Description Kevin Taylor 2004-04-06 00:53:22 AEST

Two linux boxes running 3.8p1. I log into one of the machines and run xcdroast
(for example), and the screen comes up, but as soon as something in the window
changes (highlighting a button, or clicking on a button), the window crashes
with an error like this:

Gdk-ERROR **: BadWindow (invalid Window parameter)
  serial 345 error_code 3 request_code 38 minor_code 0
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
  serial 346 error_code 10 request_code 102 minor_code 0

This does not happen when using the old ssh CLIENT to connect. So, it seems the
problem is not server related.

I will try to attach the verbose output of the session.

Comment 1 Kevin Taylor 2004-04-06 00:55:54 AEST

Created attachment 595 [details]
verbose output (X related stuff)

Comment 2 Ben Lindstrom 2004-04-06 00:58:02 AEST

This is not a bug...

man ssh_config
[..]
     ForwardX11Trusted
             If the this option is set to ``yes'' then remote X11 clients will
             have full access to the original X11 display.  If this option is
             set to ``no'' then remote X11 clients will be considered untrust-
             ed and prevented from stealing or tampering with data belonging
             to trusted X11 clients.

             The default is ``no''.

             See the X11 SECURITY extension specification for full details on
             the restrictions imposed on untrusted clients.

Comment 3 Darren Tucker 2004-04-06 01:00:26 AEST

This?
http://www.openssh.com/faq.html#3.13
[quote]
3.13 - I upgraded to OpenSSH 3.8 and some X11 programs stopped working.

As documented in the 3.8 release notes, ssh will now use untrusted X11 cookies
by default. The previous behaviour can be restored by setting ForwardX11Trusted
yes in ssh_config.
[/quote]

If this is the cause, we should update the FAQ to include the symptoms you saw.

Comment 4 Kevin Taylor 2004-04-06 01:50:25 AEST

Yes. That seems to fix it. Thanks. 

I guess I should have read the man pages over again to catch some updated options.

Comment 5 Darren Tucker 2004-04-06 08:34:22 AEST

I've added the errors you gave as examples in the FAQ entry.

Comment 6 Damien Miller 2004-04-14 12:24:20 AEST

Mass change of RESOLVED bugs to CLOSED