wine XShm problem on remote display
Alexandre Julliard
julliard at winehq.org
Tue Jun 13 09:22:17 CDT 2006
Benjamin Fabricius <benjamin.fabricius at lawo.de> writes:
> vst:/opt/fst # ./fst /mnt/testsuite/oberon4/Oberon-8.dll
> yo... lets see...
> The program 'fst.exe.so' 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 114 error_code 10 request_code 144 minor_code 1)
> (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.)
Wine will handle that error properly, but here it sounds like fst (or
more likely Gtk) has replaced the Wine error handler with its own, so
Wine doesn't get a chance to handle it.
--
Alexandre Julliard
julliard at winehq.org
More information about the wine-devel
mailing list