On Sun, Jan 15, 2017 at 8:44 PM, Jaimos Skriletz
<jaimosskril...@gmail.com> wrote:
> On Wed, Dec 28, 2016 at 3:16 AM, Dominik Vogt <dominik.v...@gmx.de> wrote:
>> On Tue, Dec 27, 2016 at 05:34:08PM -0700, Jaimos Skriletz wrote:
>>> On Tue, Dec 27, 2016 at 5:28 PM, Jaimos Skriletz
>>> <jaimosskril...@gmail.com> wrote:
>>> > On Tue, Dec 27, 2016 at 5:15 PM, Dominik Vogt <dominik.v...@gmx.de> wrote:
>>> >> On Tue, Dec 27, 2016 at 05:04:40PM -0700, Jaimos Skriletz wrote:
>>> >>> On Tue, Dec 27, 2016 at 4:52 PM, Jaimos Skriletz
>>> >>> <jaimosskril...@gmail.com> wrote:
>>> >>> > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt <dominik.v...@gmx.de> 
>>> >>> > wrote:
>>> >>> >> On Mon, Dec 26, 2016 at 01:17:05PM -0700, Jaimos Skriletz wrote:
>>> >>> >>> Hello,
>>> >>> >>>
>>> >>> >>> This was reported by a Debian user. Please retain the CC to
>>> >>> >>> 849355-forwar...@bugs.debian.org in your response, so that
>>> >>> >>> the Debian BTS has a record.
>>> >>> >>>
>>> >>> >>> In short when running FvwmIconMan, fvwm prints warnings to stderr 
>>> >>> >>> when
>>> >>> >>> opening and closing windows. I too have had this issue in 2.6.7 (and
>>> >>> >>> previous versions) so I can also say it affects my Debian system.
>>> >>> >>
>> Fixed on the (new) fvwm2-stable branch; patch for the development
>> branches will follow one I've figured out how to deal with the
>> two repositories.
>>
>
> I have the patches applied to 2.6.7 in my build and it mostly fixed
> the error (it doesn't appear with each window open/close), but I
> noticed I get a similar error when starting my config and tracked down
> FvwmButtons triggering it. The error I get is:
>
> [fvwm][GetWindowSizeHints]: <<WARNING>> reason: 2: The hints have been
> ignored because the window's current size would have become invalid.
> The new hints will become active when the window generates the next
> ConfigureRequest.
>
> [fvwm][GetWindowSizeHints]: <<WARNING>> The application window (id 0xa00004)
>   "FvwmIconMan" has broken size hints (inconsistent with current size).
>     fvwm is ignoring those hints.    hint override = 0, flags = 370
>   min_width = 200, min_height = 140, max_width = 200, max_height = 140
>   width_inc = 1, height_inc = 1
>   min_aspect = 0/0, max_aspect = 0/0
>   base_width = 0, base_height = 0
>   win_gravity = 1
>
>     If you are having a problem with the application, send a bug report
>     with this message included to the application owner.
>     There is no need to notify fvwm-workers@fvwm.org.
>
> To reproduce this
>
> 1) FvwmIconMan running with default settings,
>
> DestroyModule FvwmIconMan: *
> Module FvwmIconMan
>
> 2) Configure FvwmButtons to be just a title
>
> DestroyModuleConfig FvwmButtons: *
> *FvwmButtons: Geometry 200x200+20+20
> *FvwmButtons: Rows 1
> *FvwmButtons: Columns 1
> *FvwmButtons: (1x1, Title "Test", Frame 0)
>
> 3) Launch two instances of FvwmButtons.
>
> 4) After two instances of FvwmButtons are running, close them and the
> warning is triggered:
>

I'm also getting these errors from other applications. I will remove
the patches and see if the behvior goes back to the way it was, or if
there is something else in my system causing fvwm to output these
warnings. Here is one from a vim window.

_merge_cr_moveresize: merged 13 cr events
[fvwm][GetWindowSizeHints]: <<WARNING>> reason: 6: The hints have been
ignored because the window's current size would have become invalid.
The new hints willbecome active when the window generates the next
ConfigureRequest.

[fvwm][GetWindowSizeHints]: <<WARNING>> The application window (id 0x4200003)
  "Vim" has broken size hints (inconsistent with current size).
    fvwm is ignoring those hints.    hint override = 0, flags = 350
  min_width = 116, min_height = 92, max_width = 0, max_height = 0
  width_inc = 8, height_inc = 15
  min_aspect = 0/0, max_aspect = 0/0
  base_width = 20, base_height = 62
  win_gravity = 1

    If you are having a problem with the application, send a bug report
    with this message included to the application owner.
    There is no need to notify fvwm-workers@fvwm.org.

jaimos

Reply via email to