On Thu, 28 Jul 2022 at 12:38:10 -0500 (CDT), John D. Baker wrote: > I updated my -current install to shortly after the GCC 10.4 update, > doing a non-update build on everything. I then rebuilt all my extra > packages. > > Logging via xdm using the failsafe mode, the in-tree 'ctwm' works > fine. > Using my prefered fvwm2 (wm/fvwm), however, hangs as soon as it tries > to decorate any windows (my '.xsession' script starts 'urxvt' among > other things before exec-ing the window manager). > > The root window is mostly vacant, the undecorated icon region for > 'xconsole' is the only thing visible and the mouse cursor is the > "wristwatch" glyph. > > Switching to a text console and running 'ps' or 'top' shows the > 'fvwm2' > process is "parked". So far the only way to stop it is 'kill -9'. > > I know pkgsrc-HEAD is preferred on -current, but I'm using an up-to- > date pkgsrc-2022Q2.
I've tested fvwm on 9.99.99 builds from July 22nd and July 29th (fvwm rebuilt both times from pkgsrc HEAD), as initiated via startx, and had no issues. I also tried rxvt-unicode and didn't have any issue there, either. Perhaps there's some combination of your full setup that's tripping a regression. (I don't use xdm at all.) I've tested the following WMs and DEs and haven't found any issues (other than the one already known and addressed with Xfce): blackbox ctwm (from X base) enlightenment16 fluxbox fvwm fvwm3 icewm14 (1.4.2) jwm lxde lxqt mate openbox sawfish xfce4 Regards, Dave
