gnustep-back v. WM80.2 v. xinerama

[Armando Di Cianno]

Starting to posts to these lists more often; excuse me if this 
should've gone to the bug list, but I haven't seen any real traffic on 
that list concerning bugs. ;-)

The internals of X Shared Memory and XINERAMA are not known to me, but 
I found a strange interaction between gnustep-back, windowmaker, and 
running X in XINERAMA mode.  I'm running a recent cvs pull (060604) 
for gnustep core packages, but this problem showed up in the 'stable' 
last releases as well.  When X is run in non XINERAMA mode, there are 
no errors.  The error has to do with Shared Memory.  Output (onto the 
console X was started from) shows (LOTS!) of errors like this:

(time) (name of app)[pid] Warning: gotShmCompletion: couldn't find 
XWindowBuffer for drawable

appeaing at a rate of about 10 a second.  I'm running the art backend. 
 Everything seems to work just fine, 'cept for the unease at having 
thousands of errors messages scrolling by.

The App causing the errors at an incredible rate is AClock, which has 
a nice spinny second hand.  Other apps don't shed warnings like this 
one, but if I grab a gnustep icon and "rub it over" other icons, that 
app starts to send these messages.

This could all be an old version of WindowMaker's fault, but I figure 
I'd post and let anyone who might "just know" how to fix it know about 
it.

__armando
armando@nycap.rr.com