On Wed, Feb 15, 2017 at 6:00 AM, Vincent Lefevre <[email protected]> wrote: > Control: reopen -1 > Control: found -1 1:2.6.7-3 > > On 2017-01-20 03:05:12 +0000, Jaimos Skriletz wrote: >> Format: 1.8 >> Date: Mon, 16 Jan 2017 10:52:00 -0700 >> Source: fvwm >> Binary: fvwm >> Architecture: source amd64 >> Version: 1:2.6.7-3 >> Distribution: unstable >> Urgency: low >> Maintainer: Jaimos Skriletz <[email protected]> >> Changed-By: Jaimos Skriletz <[email protected]> >> Description: >> fvwm - F(?) Virtual Window Manager >> Closes: 849355 849422 849423 >> Changes: >> fvwm (1:2.6.7-3) unstable; urgency=low >> . >> * Updates to default configuration. >> * Improved fvwm-menu-directory error handling when python-xdg or >> a menu is not installed. >> * Fixed an issue with FvwmIconMan triggering window hit warnings. >> (Closes: #849355) >> * Added patch to improve window hit warnings (related to above). > > I still have these warnings: >
(sorry for the duplicate Vincent, didn't CC the bug report) Hello, thanks for the follow up. I too had similar warnings, but if you read through the bug report I told upstream about this and my observation was this appears to be some other bug or issue not related to the the original report which is why I closed it. The original bug in which the patch appears to have fixed is every time a Button was added/removed from FvwmIconMan causing the window to change sizes, the warning would be triggered. Now it appears to be triggered for other reasons, or at least triggered far less often (as in not every time). I get other windows, gvim being the main one, that trigger this warning. And these warnings are triggered if or if not FvwmIconMan is running. I also only get FvwmIconMan triggering this warning occasionally and not every time as what originally would happen. So at least to me the patch has done something to cut down the number of warnings. I also get other windows triggering this warning even if FvwmIconMan is not running. I will send another message upstream, but just want to double check that your observations are consistent with mine. That thought this warning still appears, it appears far less often and is not. jaimos
