Manoj Srivastava wrote:
I am curious what could have caused it - in order to compile fvwm I had to install a lot of new packages, so maybe it has to do something with that - does fvwm exectuable/FvwmEvent module have some external dependencies which, if lacking, won't prevent them from running, but will cause some features not to work?
Don't know what/whether to report it to the maintainer of the package.
I am watching. I can't reproduce this.
manoj
Maybe it is possible to reproduce the problem by installing the minimal Debian system (from stable distribution) and then using apt-get to install fvwm from unstable, so that only minimal dependencies for fvwm would be met - that is what I did. By minimal I mean only enough packages to reboot successfully.
But in order to do this, there is a need to reformat a HD to get a clean slate, and having only one HD to experiment on, and as I already spent a lot of time customizing my system I don't really want to do this.
Anyway, if nobody else had reported the problem it is probably not worth the effort.
ddtl.
-- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
