🚀 go-pugleaf

I'm running Redhat 6.0 and I'm using either Gnome or FVWM for my
X-windows. I automatically go into fvwm when I log in. 

My problem is the screensaver-clock interaction. While I am working (in
either gnome or fvwm) things are fine. As soon as the screen saver kicks
in (I go to eat something or go to class) the clock stops, then when I
move my mouse and get ready to work again, the clock starts up from
where it left off. For example, say I save a file at 09:45, and then I
go to class. When I come back 2 hours later, and immediently save a
different file, it is saved at 09:45, even though the time *should* be
11:45.

It doesn't seem to matter how long the screen saver is on, the clock
stops! I rely upon the clock display to remind me of things like class,
eating, sleeping, and stuff, so it would be really nice if it was
actually accurate. Saving files and compiling things can work on thioer
own timeframe if they really want to, I just want my clock to work. 

I have poked around the faqs, and man pages, but I can't find any
mention of the screensaver affecting the clock or how to update the
clock when it needs it. Does anyone here have a clue? (about fixing the
clock)

Xylen
-- 
  __^__                                   __^__ 
 ( ___ )---------------------------------( ___ ) 
  | / | Irony: Bill Gates claims to be    | \ | 
  | / | making a stable Operating System, | \ | 
  | / | and Linus Torvalds claims to be   | \ | 
  |___| taking over the world.            |___|
 (_____)---------------------------------(_____)