On 29 Jan 2004 00:47:49 -0600, Michael White wrote:
>
> I've been using fvwm for several years now on various platforms, and I've
> recently upgraded to an AMD 64FX51 processor, running Mandrake 9.2 RC1 for
> AMD 64 (soon to be upgraded to the shipping version). The stable RPM version
> of fvwm wouldn't install because it did not look for the 64 bit libraries, so
> I built the 2.5.8 version.
>
> The good news is that it's usable. It's never crashed, and most applications
> seem fine. The bad news is that some parts are a bit buggy. Being 2.5.8,
> I'm not sure which parts are buggy due to it being an unstable version versus
> buggy due to being compiled for 64 bit.
It is theoretically possible that some fvwm changes broke a 64 bit
architectures support.
However, your problems may probably have another explanation.
> Is there anyone else out there using a similar setup? Is there any interest
> or forum for me to bring up these bugs?
>
> Some of the things I'm seeing:
>
> - Mouse stays as "busy clock" on empty desktop
Can you reproduce this "busy clock" if you run "fvwm -f /dev/null", i.e.
fvwm without any configuration? If no, then invistigate "Wait" commands
in your configuration.
> - "FvwmButtons" icon never leaves docking panel (never finished running?)
> - Cannot click on buttons in docking panel to (de-)iconify applications
What is "docking panel"?
> - Some applications can't be moved, iconified, or resized (acroread,
> openoffice)
For each such application, send the output of "xwininfo -size" to see
whether the application indeed requested such size/position hints.
Also, try to run these applications with another window manager
(including an older fvwm version).
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 Sat Jan 31 2004 - 17:15:53 GMT