Frank Terbeck <f...@bewatermyfriend.org>:
> I've noticed this some time ago, but never had the time to look into
> it. Now that I did, I couldn't find the reason for FvwmForm's
> behaviour.
>
> What I'm seeing is the following:
> I'm using FvwmForm to query the user (me) if some action should not be
> taken if a menu entry is merely hit by accident - such as 'quit'.
>
> Now, when FvwmForm loads, I don't see any text. I can somewhat see
> where buttons would be displayed (even though they are not fully drawn
> either), but the text is entirely missing.
> All of this is happening using:
[...]
> [snip]
> % fvwm --version
> fvwm 2.5.26 compiled on May 29 2008 at 21:55:23
> with support for: ReadLine, RPlay, Stroke, XPM, PNG, SVG, Shape, XShm,
> SM, Bidi text, Xinerama, XRender, XCursor, XFT, NLS
> [snap]
>
> ...installed via debian's fvwm package version '1:2.5.26-1'.
Well... I happened to upgrade my kernel (Linux) a few days ago (from
2.6.22.19 to 2.6.27.8). And guess what, the problem vanished. I did
not upgrade my X11 installation and I'm still using the same fvwm
package form debian.
The only thing video related I changed was to enable the vesafb
framebuffer driver. I've got no idea why that should cure the problem.
In fact, I'm quite surprised this happened at all.
Anyway it seems like my setup is working again, because FvwmEvent has
not shown the weird behaviour of my previous email since.
Regards, Frank - confused, but happy
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
