Path: utzoo!utgpu!watserv1!watmath!att!rutgers!mit-eddie!bloom-beacon!EXPO.LCS.MIT.EDU!converse
From: converse@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: (none)
Message-ID: <9010191428.AA06816@excess.lcs.mit.edu>
Date: 19 Oct 90 14:28:43 GMT
References: <1990Oct19.001639.15811@rice.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 30


> Has anybody out there tried to use basic progs like xloadimage and ximage under
> the R4 twm?  

They work fine here.

> I'm having problems with these pieces of software writing to the
> colormap.  The curious thing about it is that the behavior is intermittent, in
> that sometimes the software will run fine, and then the colormap access cuts
> out after a certain time (usually about 20 mins); or the software will never be
> able to write to the colormap. 

This could be caused by the client calling XInstallColormap, which is not
compliant, or by an old bug in twm.  Fixes to twm were sent out in public 
patches #8 and #9, make sure you're running with those.  If you don't have
the most recent versions of xloadimage and ximage, get them.  You don't
say what machine you're using; the bug could be almost anywhere in the
software.

> I've been in touch with Dave Thompson at NCSA
> and he's of the opinion that twm is not ICCCM compliant and that's the problem.

R4 twm is an ICCCM-compliant window manager.  If you see evidence of 
noncompliance, regard this as a bug and send us a bug report.  The bug
report template is in doc/bugs/bug-report.

> The X gurus here at Rice think otherwise, and that there is some flag you can
> set in a .twmrc file that will make the colormap accessible.

I don't see anything in the man page about that, do you?