> I just had to restart my X server because almost all the colors in the
> default color map were reserved. I don't know what app was reserving
> them. I exited all the ones I can think of: Netscape (which I run with
> its own colormap anyway), Frame, Emacs, etc. All I had running were
> FVWM and a bunch of xterms.
I have heard of this before on this list. Think back to when you started
the X server. Some openlook programs have been known to not de-allocate
colors they allocated when starting up. In any case, every time I've
heard this problem before, it ended up being another app, not fvwm.
That doesn't mean it isn't fvwm, but try to repeat the problem...and
see if it is another app, or fvwm..
Is it possible, however, for fvwm to check the 'allocated colormap' and
find out which ones aren't being used for any app and then de-allocate them?
This sounds like a great idea for a module if it is possible.
--
Todd Fries...tfries_at_umr.edu
http://www.cs.umr.edu/~tfries
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Dec 15 1995 - 19:32:59 GMT