2010/1/8 Thomas Adam <thomas.ada...@gmail.com>: > On Fri, Jan 08, 2010 at 05:25:38PM +0100, Viktor Griph wrote: >> 2010/1/8 Jim Kalb <jimk...@gmail.com>: >> > I just tried upgrading to 2.5.28 and both stopped working. >> > >> > [...] >> > >> > So I assume that there's some generally-used window manager >> > modernization that breaks xcuckoo and probably nothing can be done about >> > it short of modifying xcuckoo (not something I'm competent to do). >> >> Can you give fvwm 2.5.27 a try? I think what you are seeing is the >> result of the "Fvwm now retains utf8 window names when the WM_NAME >> changes, and the utf8 name converted to the default charset match the >> old WM_NAME" bug fix in 2.5.28. > > Hmm. I am not so sure. The condition SET_HAS_EWMH_WM_NAME(fw, 1) for > that fix was just shifted up -- but it has always been set in > fvwm/ewmh_names.c::EWMH_WMName() to True.
The difference is that before, it would not be set if the EWMH name matched that of the classic WM_NAME exactly, which meant that it was possible to chnage the WM_NAME and have that override the name specified in _NET_WM_NAME. [1] /Viktor [1] http://www.mail-archive.com/fvwm-work...@fvwm.org/msg01954.html
