On Fri, 14 May 2004, ZXPLESPAC001, Ext wrote: > Hi, > > I have a problem with Xwin. Here are the facts: > - latest cygwin on NT4 > - remotely logued with ssh on a Linux RH Enterprise WS3 machine > - launched gvim > > Here is the error message (gvim was relaunched with '--sync'): > The program 'gvim' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadAtom (invalid Atom parameter)'. > (Details: serial 304 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.)
Check http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-ssh-no-x11forwarding > > And infos on the server: > Welcome to the XWin X Server > Vendor: The Cygwin/X Project > Release: 6.7.0.0-8 > > Contact: [EMAIL PROTECTED] > > XWin was started with the following command line: > > XWin -multiwindow -lesspointer -ac -xkbmodel pc105 -xkblayout fr -xkbvariant > nodeadkeys > > I noticed that when I launch the Xwin server with other > options (XWin -query remote_linux -nodecoration -lesspointer -ac -engine 2 > -xkbmodel pc105 -xkblayout fr -xkbvariant nodeadkeys), I haven't the > problem. Using cygwin/gvim locally on the NT machine works fine too. > > -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
