On Fri, 18 Dec 2009, Przemysław Czerpak wrote:
hi,
> Can you check if problem can be resolved if you add at the end of your
> test application:
>
> hb_gtInfo( HB_GTI_CLIPBOARDDATA, "" )
no, but i managed to strace the xterm that got picked by the Client
Killer Phenomenon.
it's last breath was this:
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 2 (X_ChangeWindowAttributes)
Resource id in failed request: 0x560001e
Serial number of failed request: 1107
Current serial number in output stream: 1108
at another try i attached xev to the victim:
this is when focus leaves the client so i can push buttons in my text
app (using sloppy focus):
FocusOut event, serial 17, synthetic NO, window 0x5a0000f,
mode NotifyNormal, detail NotifyNonlinear
this is when my test app has exited, and i focus the victim client
again. all the next events happen in a very short time right after the
pointer enters the client area:
FocusIn event, serial 17, synthetic NO, window 0x5a0000f,
mode NotifyNormal, detail NotifyNonlinear
KeymapNotify event, serial 17, synthetic NO, window 0x0,
keys: 4294967177 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
these two above events happen normally when any client gets the focus.
the below events are what seem to be coming unwanted:
UnmapNotify event, serial 17, synthetic NO, window 0x5a0000f,
event 0x5a0000f, window 0x5a0000f, from_configure NO
FocusOut event, serial 17, synthetic NO, window 0x5a0000f,
mode NotifyNormal, detail NotifyAncestor
DestroyNotify event, serial 17, synthetic NO, window 0x5a0000f,
event 0x5a0000f, window 0x5a0001a
DestroyNotify event, serial 17, synthetic NO, window 0x5a0000f,
event 0x5a0000f, window 0x5a0000f
i have just found that i've been running wm with logs saved all along
the way, and i can confirm from those logs that xterms have been
dying with the same message during all this experiment.
even more interesting.
its _only_ the xterms. i have now tried having other apps killed by
this method, but it's always the xterm that dies.
ok, i have found a pattern i seem to be able to reliably reproduce.
i am running XTerm(235) (ubuntu intrepid x64). the test app is on a
remote box, which is ubuntu karmic x64. ssh in, start the test app (it
doesn't matter whether x is via ssh or via a direct connection).
when the test app says to copy something in, copy something in from an
xterm. then push through the test app, and after it exits, give focus
to the xterm you have copied from (this may need to be done several
times). i could kill the xterm in at most 5 tries (of giving it focus,
and taking focus away from it).
i've tried other apps, xlib-based, xaw-based, gtk-based, i've even
tried rxvt, but it is invariably the xterm that dies.
i have tried XTerm(243) (this is the latest in ubuntu), same effect.
i've built myself a smokin' fresh XTerm(253), same effect.
so thus far every finger points at either xterm or xterm-wm
interaction being somehow at fault, and we could have been chasing
ghosts...
--
[-]
mkdir /nonexistent
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
