After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 155053 - remote gtk+ apps crash
remote gtk+ apps crash
Status: RESOLVED DUPLICATE of bug 136571
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2004-10-10 22:52 UTC by Joe Neeman
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joe Neeman 2004-10-10 22:52:33 UTC
Running gtk+ applications over ssh causes an X error. The same gtk+ apps work if
I copy them locally and run them. The problem seems confined to gtk+ programs;
qt and motif work fine. I have tried gtk+ 2.4.1, 2.4.5 and 2.4.9. X is xorg
version 6.8 but the problem also appears with 6.7. If you think this is an X
bug, let me know and I'll go quietly ;)

Here are some errors. What further information would be useful?
The program 'gaim' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 175 error_code 3 request_code 2 minor_code 0)
  (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.)

The program 'gkrellm2' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 1158 error_code 5 request_code 20 minor_code 0)
  (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.)
Comment 1 Owen Taylor 2004-10-11 15:01:55 UTC
Basically, the answer is 'ssh -Y'. With recent versions of ssh, ssh -X is
useless.

But we should try to fix some of these errors if they are easy to fix. 
(THere might be a bug already open on this, don't remember)
Comment 2 Owen Taylor 2004-10-12 15:12:58 UTC

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