Just a thought, but it may be the change to the /default/config
image path that was introduced into 2.6.7.
previous versions used the "--with-imagepath" value to hardcode
the system path for images. i rectified my personal build
by adding the old imagepath to fvwm/fvwm.c at the point where
it sets it to /default-config/images.
B.
Thomas Adam wrote:
On Sun, Dec 11, 2016 at 01:51:26PM +0100, Klaus Ethgen wrote:
So, I wonder, what changed that made this stuff break..
Can you send your config through, please?
-- Thomas Adam
