Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!bionet!agate!ucbvax!ucdavis!csusac!unify!Unify.com!dgh
From: dgh@Unify.com (David Harrington)
Newsgroups: comp.windows.open-look
Subject: Re: two OpenWindows problems
Message-ID: <1991Mar6.082441@Unify.com>
Date: 6 Mar 91 16:24:41 GMT
References: <1991Mar4.223608.6090@helios.physics.utoronto.ca>
Sender: news@Unify.Com (news admin)
Reply-To: dgh@Unify.com (David Harrington)
Organization: Unify Corporation, Sacramento, CA, USA
Lines: 24

In article <1991Mar4.223608.6090@helios.physics.utoronto.ca>,
rmilner@zia.aoc.nrao.edu (Ruth Milner) writes:
>
> Second, another person has noticed that if he goes away (sometimes leaving
> long jobs running in the background, sometimes not) and leaves the console
> idle for around 24 hours or longer, when he comes back and resumes work, the
> windows appear in black-and-white instead of colour, menus do not activate
> properly, etc., and he has to restart OpenWindows to get it back to normal.
> "screenblank" is running on the system (an SS1), but it activates after 10
> minutes idle time on the console, and this weirdness does not kick in until
> many hours later than that. Is the problem with screenblank, OpenWindows,
> or somehow with their interaction? Has anyone else seen or heard of this?
> 

I had a bunch of wierdness like this that I couldn't explain, either.  Looking
over the OW bug list, I noticed that there was a reported memory leak in the
xview analog clock.  I checked it out, and BOY is there!  So I started using
dclock, and everything is fine.

--
David Harrington                                  internet: dgh@eire.unify.COM
Unify Corporation                          ...!{csusac,pyramid}!unify!eire!dgh
3901 Lennane Drive                                      voice: +1 916 928-6255
Sacramento, CA 95834                                      fax: +1 916 928-6401