Community
Participate
Working Groups
1. SSH w/X tunneling 2. Start program as below 3. As soon as I move the mouse over an Eclipse window, I get the error message below. This is using Xming. I used Xming + Eclipse for several hours friday, but today it doesn't start at all. oyvind@cyviz4x4:~/download/eclipse$ ./eclipse The program 'Eclipse' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 961 error_code 3 request_code 38 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.)
Two more clues: - The splash screen window does not appear. This is using "ssh -X" - If I change command line options to "ssh -Y", I can start Eclipse fine. "ssh -X" worked friday. I don't know what changed.
Newer versions of OpenSSH changed the policy so that 'ssh -X' flags applications as untrusted. This breaks many applications, including Eclipse. The fix is to use 'ssh -Y'. This is a known issue with ssh and Eclipse. You probably upgraded your version of ssh. I have been trying to see if there's a way to modify Eclipse to work with 'ssh -X', but it's really hard and I don't think it's worth it. We're not the only application that breaks, I think xemacs is another.
(In reply to comment #2) > Newer versions of OpenSSH changed the policy so that 'ssh -X' flags >applications as untrusted. This breaks many applications, including Eclipse. >T he fix is to use 'ssh -Y'. This is a known issue with ssh and Eclipse. You > probably upgraded your version of ssh. I didn't upgrade SSH since friday. IMHO, a perfectly reasonable resolution to this issue would be an informative error message from Eclipse. Øyvind
If you haven't upgraded ssh, the only thing I can think of is that something you did in Eclipse causes you to now hit a code path that leads to this error. I don't think there's any way that I can detect this error and show a dialog. The problem is that AFAICT ssh simply flags the connection as untrusted, and then the X server at the other end decides the policy on what it will allow or not. A BadWindow error could be a bug in Eclipse -- I have no way of knowing if it is because this particular X server decided the request was disallowed.
I am tracking issues with ssh -X vs -Y in bug 94477. *** This bug has been marked as a duplicate of 94477 ***
(In reply to comment #4) > If you haven't upgraded ssh, the only thing I can think of is that something > you did in Eclipse causes you to now hit a code path that leads to this error. > > I don't think there's any way that I can detect this error and show a dialog. > The problem is that AFAICT ssh simply flags the connection as untrusted, and > then the X server at the other end decides the policy on what it will allow or > not. A BadWindow error could be a bug in Eclipse -- I have no way of knowing > if it is because this particular X server decided the request was disallowed. These cribs are no help? - The splash screen didn't show. - The requester asking for the location of the workspace did show. - The crash happened when I moved the mouse over the requester asking for the location of the workspace. Anything more I can do? Øyvind
I don't know why the splash wouldn't show. I think you're seeing the same sort of crash that I saw in bug 94477. I don't think it would be a good idea though to assume that any BadWindow from a mouse position request is because of a permissions problem. IMHO, you should push OpenSSH to pop up a warning or similar when using ssh -X to indicate that applications may crash. Eclipse isn't the only one that has bad problems.
