Hi,
On Wed, Aug 31, 2011 at 07:53:03PM +0000, vik wrote:
> Any help would be much appreciated - here are the details -
>
> vncserver version -
> vnc/E4.4.2/vncserver
>
> fvwm2 version -
> fvwm2/2.5.17/bin/fvwm2
That's an old version of FVWM. Do you have reason to use this? Please try
with FVWM 2.6.2, and if necessary if your package manager doesn't provide
that version you'll have to compile it manually.
Regardless of your reasons why FvwmButtons isn't started (and it's not
obvious from your example why), the syntax for module options as you have
them has changed. Module aliases have looked like this for a long time now:
*AliasName: option values
> *FvwmButtonsRows 10
> *FvwmButtonsBoxSize smart
> *FvwmButtonsFrame 1
> *FvwmButtonsGeometry +275-1
> *FvwmButtonsPadding 0 0
> *FvwmButtonsBack gray60
... as you can see from this example, even though it's still supported, you
should be using:
*FvwmButtons: Rows 10
*FvwmButtons: BoxSize smart
etc.
Note also that using the alis of FvwmButtons directlyy is perhaps not what
you want. Whilst it means that you can do this:
AddToFunc StartFunction I Module FvwmButtons
You're better off defining a unique alias for any FvwmButtons instance and
using that instead. Hence:
*FooFvwmButtons: ....
AddToFunc StartFunction I Module FvwmButtons FooFvwmButtons
Unfortunately what you've sent through doesn't tell me how FvwmButtons is
started. If you send me your entire config, maybe I can help you convert it
over to something more modern as well.
Note also that you should be checking STDERR for anything, and typically
FVWM will log to ~/.xsession-errors, unless you tell X11 otherwise.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
