Is this an X bug, an ssh bug, or what?
I often ssh with X11 forwarding into other systems, and with depressing regularity I get X errors the first time I run gtk apps like gedit, synaptic, etc:
The program 'synaptic' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 442 error_code 10 request_code 148 minor_code 5) (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.)
If I immediately try to run the exact same app a second time, it works perfectly.
Anyone seen anything like this? Anyone know what is going on?
My host system I am running ssh from is always a fedora 8 system because that is what is on my desktops, so I can't say if it happens with other kinds of hosts or not.
Sometimes I don't get that error right away, but the app will come up and things like icons will be missing, then I'll get a similar error a little later (perhaps when trying to popup some dialog).
Should I be trying ssh -Y instead of ssh -X (which my fingers type from reflex)? I have to say I have no idea what the man page is talking about with the difference between -X and -Y.
2008/5/6 Tom Horsley tom.horsley@att.net:
Is this an X bug, an ssh bug, or what?
I often ssh with X11 forwarding into other systems, and with depressing regularity I get X errors the first time I run gtk apps like gedit, synaptic, etc:
The program 'synaptic' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 442 error_code 10 request_code 148 minor_code 5) (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.)
If I immediately try to run the exact same app a second time, it works perfectly.
Anyone seen anything like this? Anyone know what is going on?
My host system I am running ssh from is always a fedora 8 system because that is what is on my desktops, so I can't say if it happens with other kinds of hosts or not.
Sometimes I don't get that error right away, but the app will come up and things like icons will be missing, then I'll get a similar error a little later (perhaps when trying to popup some dialog).
Should I be trying ssh -Y instead of ssh -X (which my fingers type from reflex)? I have to say I have no idea what the man page is talking about with the difference between -X and -Y.
This looks like:
http://openssh.com/faq.html#3.13
If that doesn't solve your issue, then file a bug.
HTH, Jonathan.
On Tue, 6 May 2008 23:43:59 +0100 "Jonathan Underwood" jonathan.underwood@gmail.com wrote:
Should I be trying ssh -Y instead of ssh -X (which my fingers type from reflex)? I have to say I have no idea what the man page is talking about with the difference between -X and -Y.
This looks like:
http://openssh.com/faq.html#3.13
If that doesn't solve your issue, then file a bug.
Yea, using "trusted" X11 forwarding (whatever the $#@! that is :-) fixes the problem, but I still can't wrap my brain around why the program always works on the 2nd try. If it is the same dadgum program, won't it be doing the same untrusted operation the second time I run it?
It is behavior like this what causes unrest (to paraphrase Monty Python :-).