Hi Hans,

> Perhaps it is not a Fvwm problem then if my config shouldn't fix  
> anything maybe we (Alexander and I) should compare package and/or fvwm  
> versions for Ubuntu (I run "recent" CVS version).

Good idea, though I observe these problems still quite some time across
several updates.

   $ fvwm --version
   fvwm 2.5.26 compiled on Jun  1 2008 at 16:06:59

   $  apt-cache policy fvwm
   fvwm:
     Installed: 1:2.5.26-1
     Candidate: 1:2.5.26-1

Cheers,
- Alex

Reply via email to