i tried running a couple apps in wine remotely, piping X to my
powerbook w/ OS 10.4.6 which otherwise works fine. thus i think this
is wine- or app-specific. i get similar errors (see below) in
different apps. on the surface, looks like bad window or pointer.
i figure wine can't find the right libs for display on the client... do
i just need a PATH to my the libs on my client? e.g. couldn't i just
copy all the wine stuff into /some/directory on the client?
-bryan
------- BEGIN BACKTRACE ----------
[ myprompt 10:56:06 ] app1
err:ntdll:RtlpWaitForCriticalSection section 0x7b8f2fe0 "syslevel.c:
Win16Mutex" wait timed out in thread 0009, blocked by 000a, retrying
(60 sec)
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 38 (X_QueryPointer)
Resource id in failed request: 0x57
Serial number of failed request: 143
Current serial number in output stream: 143
or
[ myprompt 10:56:33 ] app2
fixme:ole:CoRegisterMessageFilter stub
fixme:ole:OleLoadPictureEx
(0x41b00a9c,774,0,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x405efae8),
partially implemented.
fixme:ole:OleLoadPictureEx
(0x41b00a9c,774,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x405efab8),
partially implemented.
fixme:ole:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0
palette.
fixme:ole:OleLoadPictureEx
(0x41b00a9c,774,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x405efab8),
partially implemented.
fixme:ole:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0
palette.
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 38 (X_QueryPointer)
Resource id in failed request: 0x57
Serial number of failed request: 105
Current serial number in output stream: 105
salmonrushdee <bryanlepore@gmail.com> wrote:> X Error of failed request: BadWindow (invalid Window parameter) > Major opcode of failed request: 38 (X_QueryPointer) > Resource id in failed request: 0x57 > Serial number of failed request: 143 > Current serial number in output stream: 143I have seen this happening before. Are you tunneling X11 over ssh? If yes, try using ForwardX11Trusted instead of ForwardX11 or vice versa and see if that changes anything. Daniel
----- Original Message ---- From: salmonrushdee <bryanlepore@gmail.com> To: wine-users@winehq.org Sent: Wednesday, May 3, 2006 9:14:43 AM Subject: [Wine] BadWindow : X or Wine or... i tried running a couple apps in wine remotely, piping X to my powerbook w/ OS 10.4.6 which otherwise works fine. thus i think this is wine- or app-specific. i get similar errors (see below) in different apps. on the surface, looks like bad window or pointer. i figure wine can't find the right libs for display on the client... do i just need a PATH to my the libs on my client? e.g. couldn't i just copy all the wine stuff into /some/directory on the client? -bryan I'm not sure how much this will help you, but a year or two ago, I did something similar. I had Wine running on a Linux box. Then from a Solaris 9 client, I "SSH -x"ed into the Linux box. From there, I ran the app with the usual wine "c:\Program Files\blah blah blah.exe" command, and the application showed up on my Solaris desktop. Hiji
hi all, everyone honed in on -X and forwarding, because i failed to emphasize... or even mention... that the app window actually appears in all its glory on the client, until BANG it crashes with the trace i posted. soooo... i think i'm still stuck. sorry about the mistake. -bryan
salmonrushdee wrote:> X Error of failed request: BadWindow (invalid Window parameter) > Major opcode of failed request: 38 (X_QueryPointer) > Resource id in failed request: 0x57 > Serial number of failed request: 143 > Current serial number in output stream: 143Might be helpful: # google XQueryPointer http://www.xfree86.org/current/XQueryPointer.3.html # cd wine-git/dlls/x11drv # grep -R XQueryPointer * | grep -v Binary event.c: XQueryPointer( event->display, win, &w_aux_root, &w_aux_child, event.c: XQueryPointer( event->display, root_window, &u.w_aux, &u.w_aux, event.c: XQueryPointer( event->display, root_window, &root, &child, mouse.c: if (XQueryPointer( display, root_window, &root, &child, You could add a TRACE that prints the window handle it's trying to find to the above 4 calls. Or perhaps something like this would be helpful: # WINEDEBUG=+trace wine app1 2>&1 | grep -E 'CreateWindow|QueryPointer'