Bug 82798

Summary: up2date X error over ssh
Product: Red Hat Enterprise Linux 4 Reporter: Need Real Name <jcromie>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satellite-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 4.0CC: rhn-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-02 19:18:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Need Real Name 2003-01-26 18:50:48 UTC
Description of problem:

when I start up2date over an ssh connection (over internet),
up2ate errors, as follows:

[root@homer root]# up2date
The program 'up2date' received an X Window System error.
This probably reflects a bug in the program.
The error was '202'.
  (Details: serial 379 error_code 202 request_code 155 minor_code 8)
  (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.)
[root@homer root]# 

stopping iptables on both ends has no effect, 
nor does `xhost +` on my end (not homer)

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

[root@homer root]# rpm -q up2date
up2date-3.0.7-1

How reproducible:  every time, across inet.  Dunno how it behaves locally



Steps to Reproduce:
1.
2.
3.
    
Actual results: see above


Expected results:


Additional info: