Icon labels blank sometimes w/ FVWM 3

Hello world!

I recently upgraded from fvwm2 to fvwm3 1.0.5 (1.0.4-135-gc8763635), built locally from git sources. For the most part it’s been going swimmingly, and several past issues/limitations with fvwm2 have been resolved, so yay progress.

I am noticing one glitch that’s new with fvwm3: Sometimes icon labels get blanked out. It seems like it’s 100% reproducible by maximizing a window, then un-maximizing. The icon itself looks fine, but there’s just a blank rectangle (of label background color) where the text should be.

Merely dragging a window over the icon does not do it, nor does popping up a window over the icon and then closing it. Once the problem manifests, dragging a window over the icon, or popping a window over it, makes it appear properly again. Rebooting doesn’t help. It appears in a screenshot so I don’t think it’s a video card problem.

It’s not really bothering me much, but in the spirit of reporting new issues, I figured I should mention it. If there’s anything I can do to help track down the issue, please let me know.


Screen shot. The icon pictured in the center near the top is as I see it on my screen. (My dock appears unaligned because my lower monitor is narrower than my upper monitor. The area to the left of the dock is off-monitor.)


My FVWM config tree:


Xorg log file from the same session as screenshot:



  • Debian 11.4 “bullseye”
    • Linux 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64
    • X.Org X Server 1.20.11 (deb pkg 2:1.20.11-1+deb11u2)
    • radeon_drv.so 19.1.0 (deb pkg 1:19.1.0-2)
    • GCC 10.2.1 20210110 (Debian 10.2.1-6)
    • fvwm3 1.0.5 (1.0.4-135-gc8763635)
  • Dell Precision T3400
    • VisionTek VTK6350 (ATI Radeon HD 5450, ChipID 0x68f9, 1 GB RAM)
    • Intel Core 2 Duo E6850 (2 x 3 GHz)
    • 8 GB main RAM
    • HP LA2306x LCD (upper)
    • Dell 2005FPW LCD (lower)

X server layout

HP LA2306x is running at 1920x1080 and is at position 0,0.

Dell 2005FPW is running at 1680x1050 and is at position 120,1080. It’s designated “Primary”.

Hi @DragonHawk

Thanks. Please can you transfer all of this information to Github’s issue tracker?

See: Issues · fvwmorg/fvwm3 · GitHub

Oh, right, git. I keep forgetting about all these new-fangled tools. Back in my day, etc., etc. :-)

New issue opened:


For the benefit of archives/searches…

The problem was traced to this function:

DestroyFunc	MaximizeAndRaise
AddToFunc	MaximizeAndRaise
+ I Maximize
+ I Raise

Commenting out the I Raise made the problem go away. This proved to be an adequate workaround:

+ I Schedule 100 Raise

My thanks to Mr. Adam for his help.

1 Like