Received: (at submit) by bugs.debian.org; 18 Dec 1997 17:59:20 +0000 Received: (qmail 21002 invoked from network); 18 Dec 1997 17:59:18 -0000 Received: from paycheck.thok.org (HELO kitten.gen.ma.us) (paycheck.thok.org@199.103.225.1) by 205.229.104.5 with SMTP; 18 Dec 1997 17:59:18 -0000 Received: (qmail 9892 invoked by uid 3382); 18 Dec 1997 18:07:49 -0000 To: submit@bugs.debian.org Subject: xlockmore seems to run out of colormap entries From: eichin@kitten.gen.ma.us (Mark W. Eichin) Date: 18 Dec 1997 13:07:49 -0500 Message-ID: Lines: 16 X-Mailer: Gnus v5.4.56/Emacs 19.34 Package: xlockmore Version: 4.06.1-1 I often run xlock with no arguments, and no xlock-specific resources, for hours, even days at a time. I've noticed recently that "braid" in particular gets a scrambled colormap -- if you start "xlock -mode braid" it looks fine, but if you run xlock for 8 hours or so (cycling through other modes), you will probably see braid show up in a mode where the colors are in fragments, instead of a continuous range. xlock doesn't print any messages when this happens, though. I don't think I ever saw this in a version of xlock that didn't have the cool new 3d effects, but I can't guarantee that that was the triggering change. If you'd like me to run a version with some debugging output in it overnight some time, I can do that if it would help...