On Fri, 18 Dec 2009, Tamas TEVESZ 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 [...] > 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. Now it seems to be a little bit different thing the one you described in previous message or maybe I didn't understood you correctly. > 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). I fixed stupid bug in one of last commits which was exploited on 64bit machines so if possible please check if you can still replicate the problem with current SVN code. Anyhow seems that this modification should not effect any valid 3-rd party code. > 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... I cannot replicate it (probably because I cannot exactly replicate your environment settings) so I have to guess but probably you are right. Anyhow thank you very much for your tests. Finally I've found a while to clean the selection code in GTXWC. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
