On 03 Sep 2002 12:02:41 +0000, Bruce M Beach wrote:
>
> 1) I am at this point using 2.5.2 more or less because I have to.
> I used a very early version of fvmw for years with no problems
> and then upgraded to xwindows 4.2 which caused significant problems
> with the mouse-menu interaction. An upgrade to fvwm-2.4.8 did not
> solve the problems whereas the alpha version fvwm-2.5.2 did. I've
> used fvwm-2.5.2 for a while now and for my use it works fine.
> With fvwm-2.5.3 the problems started again.
I think your short description (in another thread) is not enough to
understand the problem. Please add more details to that message.
What is the "mouse-menu" problem and what to do exactly to reproduce it.
> 2) It looks like the following are not getting execute permission
> when installed. For instance:
> sh-2.05b# fvwm-bug
> sh: /usr/local/bin/fvwm-bug: Permission denied
> A chmod fixes it.
>
> fvwm-bug
> fvwm-config
> fvwm-convert-2.4
> fvwm-convert-2.6
> fvwm-menu-desktop
> fvwm-menu-directory
> fvwm-menu-headlines
> fvwm-menu-xlock
> fvwm-perllib
Seems unlikely to me that they are installed without a+x.
Please do the following:
#cd fvwm_installation_dir
cd bin/
make uninstall # as root
make
make install # as root
Then send the output of "make install" and "ls -l /usr/local/bin/fvwm-*".
> 3) I built with the following configure options
> --enable-debug-msgs
> --enable-command-log
> and it builds fine but I don't understand where the messages
> get piped to. syslogd? an fvwm console?
This depends on how you start the fvwm executable. If you call it in
~/.xinitrc without redirection to a file, the output will be together
with the X output, possibly on your virtual console.
Display managers like xdm/gdm/kdm may redirect the output to a file.
I don't think these debugging options are very useful to you, the output
is noisy and hides the real error messages that may appear on stderr.
Regards,
Mikhael.
--
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 Tue Sep 03 2002 - 03:33:04 BST