On Thu, Aug 23, 2001 at 10:00:59PM -0500, Stephen wrote:
> On Thu, Aug 23, 2001 at 08:21:41PM +0000, Mikhael Goikhman wrote:
> > On 23 Aug 2001 11:12:02 -0500, Stephen wrote:
> > >
> > > I recently moved from fvwm 2.2.4 to 2.4.0. I use the clock program
> > > "oclock" with the transparent option, and noticed with fvwm 2.4.0 it
> > > doesn't update the background behind the clock. The clock hands smear as
> > > they advance. Since I've tried 2.4.0 on both Solaris and FreeBSD with the
> > > same result, my guess is I'm missing something in fvwm's config file.
> >
> > Please run oclock without FVWM to see whether the problem is in oclock or
> > in X. You may do this in several ways, for example, while in FVWM execute
> > "Restart xterm" from FvwmTalk or FvwmConsole. Then start oclock in xterm.
> > To return to FVWM, type "fvwm2" in xterm.
> >
> > Regards,
> > Mikhael.
>
> First, I forgot to mention before that I'm not on the list. Please cc all
> replies to my email address.
>
> In my .xinitrc file I replaced "exec fvwm2" with "exec xterm". I ran an
> oclock from within that xterm and it functions properly.
>
> As for my fvwm2, I compiled it very minimally (if that makes a difference).
> Here's the "fvwm-config -info" output:
>
[...]
I used the FreeBSD fvwm2 package instead, which includes:
Support for features:
readline: yes
rplay: no
stroke: no
xpm: yes
gnome-wm (window manager hints): no
sm (session management): yes
gtk (FvwmGtk): yes
gdk-imlib (in FvwmGtk): yes
gnome-libs (in FvwmGtk): no
multibyte: no
And oclock works correctly.
Thanks for the help,
Steve
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Aug 23 2001 - 22:10:31 BST