On Fri, Sep 05, 2014 at 04:08:09PM -0400, Chris Siebenmann wrote: > > Could one of you please try what happens if you add the following > > lines at the end of the function fvwm/icons.c:CMD_Iconify(), right > > before the final return: > > > > FlushAllMessageQueues(); > > XFlush(dpy); > > EWMH_SetWMState(fw, False); > > GNOME_SetHints(fw); > > GNOME_SetWinArea(fw); > > > > (Even if it works it is not a proper solution, just an attempt to > > fire extra events at the window and see what happens.) > > I tried this and it appears to have made no difference to the > behavior of Chrome: de-iconifying still results in blank white, > and WindowShade'ing it fixes this.
Sigh. Do you use any of the window shading related styles? WindowShadeSteps WindowShadeScrolls or WindowShadeShrinks WindowShadeLazy or WindowShadeAlwaysLazy or WindowShadeBusy Or the obsolete WindowShadeAnimate command? Can you post all your WindowShade related settings please? And what exactly is the command that triggers shading? (All these questions aim at finding out exactly what the WindowShade command does on your system, and what the difference is between shading and resizing windows manually.) Also, please try to grab the bottom border of the bad window, and drag it all the way up to the title bar (in opaque resize mode, not in wire frame mode). Stop resizing, then resize the window again to its original size. One more thing to try: Does maximizing and unmaximizing the window help? Or making it sticky and unsticky? Ciao Dominik ^_^ ^_^ -- Dominik Vogt
