Bug 147294

Summary: BadWindow / BadAtom error in ssh X11 forwarding
Product: [Fedora] Fedora Reporter: Robert K. Moniot <moniot>
Component: opensshAssignee: Tomas Mraz <tmraz>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-07 03:07:52 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Robert K. Moniot 2005-02-06 10:59:07 EST
Description of problem:

From an X session, connect to local or remote host using ssh with X11
forwarding.  Fire up an application, e.g. xterm or emacs and select
some text by clicking and dragging mouse.  Application dies with error
message such as:
X Error of failed request:  BadAtom (invalid Atom parameter)
    Major opcode of failed request:  18 (X_ChangeProperty)
    Atom id in failed request:  0x1a8
    Serial number of failed request:  208
    Current serial number in output stream:  210


X protocol error: BadWindow (invalid Window parameter) on protocol
request 38

Workaround: this behavior goes away if ssh -Y option is used or
ForwardX11Trusted=yes is in ssh_config.

Version-Release number of selected component (if applicable):

How reproducible: always

Steps to Reproduce:
1. log on to X
2. ssh somehost
3. xterm &
4. click and drag mouse over some text
Actual results:
program dies and closes window with BadWindow or BadAtom error

Expected results:
program should continue running with text selected

Additional info:
for an independent report.
Comment 1 Robert K. Moniot 2005-02-06 11:03:30 EST
I did some more searching and it seems this is a documented feature,
not a bug.  See http://www.openssh.com/faq.html item 3.13 
Comment 2 Sitsofe Wheeler 2005-02-06 14:35:03 EST
Yup, it's mentioned in the FC3 release notes too. This a dup of bug #137685
Comment 3 Tomas Mraz 2005-02-07 03:07:52 EST

*** This bug has been marked as a duplicate of 137685 ***