Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Sun, Jan 15, 2017 at 10:10 PM, Jaimos Skriletz wrote: > On Sun, Jan 15, 2017 at 8:44 PM, Jaimos Skriletz > wrote: >> On Wed, Dec 28, 2016 at 3:16 AM, Dominik Vogt 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 wrote: > On Tue, Dec 27, 2016 at 5:15 PM, Dominik Vogt > 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 >>> wrote: >>> > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt >>> > 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'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. > After further investigation these new warnings do not seem related to the original bug as they occur with or without the patches in question. If I remove the patches I get the old behavior back. And without the patches I still get gvim and other windows giving warnings. I wonder if there is something new going on on my system in the other applications causing these warnings or if they were there before, I just didn't notice in the spam of the ones from FvwmIconMan. Anyways thanks again for your help on this. jaimos
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Sun, Jan 15, 2017 at 8:44 PM, Jaimos Skriletz wrote: > On Wed, Dec 28, 2016 at 3:16 AM, Dominik Vogt 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 >>> wrote: >>> > On Tue, Dec 27, 2016 at 5:15 PM, Dominik Vogt 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 >>> >>> wrote: >>> >>> > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt >>> >>> > 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]: <> 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]: <> The application window (id 0xa4) > "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]: <> 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]: <> The application window (id 0x423) "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
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Wed, Dec 28, 2016 at 3:16 AM, Dominik Vogt 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 >> wrote: >> > On Tue, Dec 27, 2016 at 5:15 PM, Dominik Vogt 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 >> >>> wrote: >> >>> > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt >> >>> > 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]: <> 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]: <> The application window (id 0xa4) "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: When playing around with this I sometimes get the warning triggered when I start FvwmButtons. I can always get it to trigger if I have more than one instance running. I don't seem to get these warnings launching xterms or closing them. Unsure if it is related to FvwmButtons, but my more complicated FvwmButtons setup seems to trigger this every time fvwm starts. jaimos
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Wed, Dec 28, 2016 at 3:16 AM, Dominik Vogt 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 >> wrote: >> > On Tue, Dec 27, 2016 at 5:15 PM, Dominik Vogt 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 >> >>> wrote: >> >>> > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt >> >>> > 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. >> >>> >> >> >>> >> >> >>> >> I don't get any such messages with or without FvwmIconMan. Can >> >>> >> you give detailed instructions pelase? >> >>> >> >> >>> > >> >>> > Using Fvwm 2.6.7 Debian package, doubt it is any of the debian >> >>> > patches, but I will compile a version without patches and test. >> >>> > >> >>> >> >>> Tested with a fresh compile of Fvwm 2.6.7 without any debian patches, >> >>> same issue. >> >>> >> >>> > >> Further testing, if I set the ManagerGeometry to something like 5x3 so >> FvwmIconMan doesn't resize itself, I no longer get the warning. It is >> only with the default like 0x1, causing the window to grow/shrink I >> get the warning. > > Could be reproduced with a standalone FvwmIconMan (instead of the > one inside FvwmButtons). > Good, I thought I said it had to be stand alone in my description, glad you were able to track it down. >> Wild guess, could it be some timing issue during the resizing of the >> window when adding/removing a button cause the window's current size >> to become invalid as per the warning? > > Roughly, yes. FvwmIconMan sets the minimum and maximum width and > height size hints to the new geometry it wants, then requests the > new size. When fvwm reads the new hints, the current geometry of > the manager window becomes obviously invalid until the window is > also resized. That's what triggers the warning. > > So, to fix this: > > 1. Remove the size restrictions, then resize, then set the new >size restrictions. Theoretically the winodw might be resized >by the user in between, but that's highly unlikely. > > 2. Also print the size hints that trigger this warning in a second >message. > > 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. > Thanks, though I think there is some confusion about what is the 'stable' branch and 'development' branch(s) right now. Anyways I'll send another email about this. jaimos
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Tue, Dec 27, 2016 at 05:34:08PM -0700, Jaimos Skriletz wrote: > On Tue, Dec 27, 2016 at 5:28 PM, Jaimos Skriletz > wrote: > > On Tue, Dec 27, 2016 at 5:15 PM, Dominik Vogt 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 > >>> wrote: > >>> > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt > >>> > 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. > >>> >> > >>> >> > >>> >> I don't get any such messages with or without FvwmIconMan. Can > >>> >> you give detailed instructions pelase? > >>> >> > >>> > > >>> > Using Fvwm 2.6.7 Debian package, doubt it is any of the debian > >>> > patches, but I will compile a version without patches and test. > >>> > > >>> > >>> Tested with a fresh compile of Fvwm 2.6.7 without any debian patches, > >>> same issue. > >>> > >>> > > >>> > I tested this with other windows and modules. FvwmScript modules > >>> > seemed to trigger it, FvwmIdentify did not, so I wonder if it has to > >>> > do with transient windows or not (just something I noticed). > >>> > > >>> > >>> Nevermind this, FvwmIdentify is not a traisnent window, the reason it > >>> was not producing the warning was it was configured so FvwmIconMan did > >>> not create a button for that window. > >>> > >>> After further testing the warning seems to be due to be caused by > >>> adding/removing the button for a window from FvwmIconMan. Windows that > >>> appear there trigger the warning but ones that don't appear don't. > >> > >> Still no luck to reproduce it. After said message there should > >> always be this one which prints all the details of the window and > >> the faulty hints: > >> > >> fvwm_msg( > >> WARN, "GetWindowSizeHints", > >> "The application window (id %#lx)\n" > >> " \"%s\" has broken size hints (%s).\n" > >> "fvwm is ignoring those hints. " > >> " hint override = %d, flags = %lx\n" > >> " min_width = %d, min_height = %d, " > >> "max_width = %d, max_height = %d\n" > >> " width_inc = %d, height_inc = %d\n" > >> " min_aspect = %d/%d, max_aspect = %d/%d\n" > >> " base_width = %d, base_height = %d\n" > >> " win_gravity = %d\n", > >> > > > > I get no other output after the warning, so that message is never > > printed to stderr on my system. > > > > Unsure if this helps, but I did enable BugOpts DebugCRMotionMethod, > > and get the output > > > > _cdim: not moved 0x55927d4a8990 'FvwmIconMan' > > > > after each time the warning is produced. > > Further testing, if I set the ManagerGeometry to something like 5x3 so > FvwmIconMan doesn't resize itself, I no longer get the warning. It is > only with the default like 0x1, causing the window to grow/shrink I > get the warning. Could be reproduced with a standalone FvwmIconMan (instead of the one inside FvwmButtons). > Wild guess, could it be some timing issue during the resizing of the > window when adding/removing a button cause the window's current size > to become invalid as per the warning? Roughly, yes. FvwmIconMan sets the minimum and maximum width and height size hints to the new geometry it wants, then requests the new size. When fvwm reads the new hints, the current geometry of the manager window becomes obviously invalid until the window is also resized. That's what triggers the warning. So, to fix this: 1. Remove the size restrictions, then resize, then set the new size restrictions. Theoretically the winodw might be resized by the user in between, but that's highly unlikely. 2. Also print the size hints that trigger this warning in a second message. 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. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Tue, Dec 27, 2016 at 5:28 PM, Jaimos Skriletz wrote: > On Tue, Dec 27, 2016 at 5:15 PM, Dominik Vogt 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 >>> wrote: >>> > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt 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. >>> >> >>> >> >>> >> I don't get any such messages with or without FvwmIconMan. Can >>> >> you give detailed instructions pelase? >>> >> >>> > >>> > Using Fvwm 2.6.7 Debian package, doubt it is any of the debian >>> > patches, but I will compile a version without patches and test. >>> > >>> >>> Tested with a fresh compile of Fvwm 2.6.7 without any debian patches, >>> same issue. >>> >>> > >>> > I tested this with other windows and modules. FvwmScript modules >>> > seemed to trigger it, FvwmIdentify did not, so I wonder if it has to >>> > do with transient windows or not (just something I noticed). >>> > >>> >>> Nevermind this, FvwmIdentify is not a traisnent window, the reason it >>> was not producing the warning was it was configured so FvwmIconMan did >>> not create a button for that window. >>> >>> After further testing the warning seems to be due to be caused by >>> adding/removing the button for a window from FvwmIconMan. Windows that >>> appear there trigger the warning but ones that don't appear don't. >> >> Still no luck to reproduce it. After said message there should >> always be this one which prints all the details of the window and >> the faulty hints: >> >> fvwm_msg( >> WARN, "GetWindowSizeHints", >> "The application window (id %#lx)\n" >> " \"%s\" has broken size hints (%s).\n" >> "fvwm is ignoring those hints. " >> " hint override = %d, flags = %lx\n" >> " min_width = %d, min_height = %d, " >> "max_width = %d, max_height = %d\n" >> " width_inc = %d, height_inc = %d\n" >> " min_aspect = %d/%d, max_aspect = %d/%d\n" >> " base_width = %d, base_height = %d\n" >> " win_gravity = %d\n", >> > > I get no other output after the warning, so that message is never > printed to stderr on my system. > > Unsure if this helps, but I did enable BugOpts DebugCRMotionMethod, > and get the output > > _cdim: not moved 0x55927d4a8990 'FvwmIconMan' > > after each time the warning is produced. Further testing, if I set the ManagerGeometry to something like 5x3 so FvwmIconMan doesn't resize itself, I no longer get the warning. It is only with the default like 0x1, causing the window to grow/shrink I get the warning. Wild guess, could it be some timing issue during the resizing of the window when adding/removing a button cause the window's current size to become invalid as per the warning? jaimos
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Tue, Dec 27, 2016 at 5:15 PM, Dominik Vogt 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 >> wrote: >> > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt 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. >> >> >> >> >> >> I don't get any such messages with or without FvwmIconMan. Can >> >> you give detailed instructions pelase? >> >> >> > >> > Using Fvwm 2.6.7 Debian package, doubt it is any of the debian >> > patches, but I will compile a version without patches and test. >> > >> >> Tested with a fresh compile of Fvwm 2.6.7 without any debian patches, >> same issue. >> >> > >> > I tested this with other windows and modules. FvwmScript modules >> > seemed to trigger it, FvwmIdentify did not, so I wonder if it has to >> > do with transient windows or not (just something I noticed). >> > >> >> Nevermind this, FvwmIdentify is not a traisnent window, the reason it >> was not producing the warning was it was configured so FvwmIconMan did >> not create a button for that window. >> >> After further testing the warning seems to be due to be caused by >> adding/removing the button for a window from FvwmIconMan. Windows that >> appear there trigger the warning but ones that don't appear don't. > > Still no luck to reproduce it. After said message there should > always be this one which prints all the details of the window and > the faulty hints: > > fvwm_msg( > WARN, "GetWindowSizeHints", > "The application window (id %#lx)\n" > " \"%s\" has broken size hints (%s).\n" > "fvwm is ignoring those hints. " > " hint override = %d, flags = %lx\n" > " min_width = %d, min_height = %d, " > "max_width = %d, max_height = %d\n" > " width_inc = %d, height_inc = %d\n" > " min_aspect = %d/%d, max_aspect = %d/%d\n" > " base_width = %d, base_height = %d\n" > " win_gravity = %d\n", > I get no other output after the warning, so that message is never printed to stderr on my system. Unsure if this helps, but I did enable BugOpts DebugCRMotionMethod, and get the output _cdim: not moved 0x55927d4a8990 'FvwmIconMan' after each time the warning is produced.
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Tue, Dec 27, 2016 at 05:04:40PM -0700, Jaimos Skriletz wrote: > On Tue, Dec 27, 2016 at 4:52 PM, Jaimos Skriletz > wrote: > > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt 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. > >> > >> > >> I don't get any such messages with or without FvwmIconMan. Can > >> you give detailed instructions pelase? > >> > > > > Using Fvwm 2.6.7 Debian package, doubt it is any of the debian > > patches, but I will compile a version without patches and test. > > > > Tested with a fresh compile of Fvwm 2.6.7 without any debian patches, > same issue. > > > > > I tested this with other windows and modules. FvwmScript modules > > seemed to trigger it, FvwmIdentify did not, so I wonder if it has to > > do with transient windows or not (just something I noticed). > > > > Nevermind this, FvwmIdentify is not a traisnent window, the reason it > was not producing the warning was it was configured so FvwmIconMan did > not create a button for that window. > > After further testing the warning seems to be due to be caused by > adding/removing the button for a window from FvwmIconMan. Windows that > appear there trigger the warning but ones that don't appear don't. Still no luck to reproduce it. After said message there should always be this one which prints all the details of the window and the faulty hints: fvwm_msg( WARN, "GetWindowSizeHints", "The application window (id %#lx)\n" " \"%s\" has broken size hints (%s).\n" "fvwm is ignoring those hints. " " hint override = %d, flags = %lx\n" " min_width = %d, min_height = %d, " "max_width = %d, max_height = %d\n" " width_inc = %d, height_inc = %d\n" " min_aspect = %d/%d, max_aspect = %d/%d\n" " base_width = %d, base_height = %d\n" " win_gravity = %d\n", Ciao Dominik ^_^ ^_^ -- Dominik Vogt
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Tue, Dec 27, 2016 at 4:52 PM, Jaimos Skriletz wrote: > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt 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. >> >> >> I don't get any such messages with or without FvwmIconMan. Can >> you give detailed instructions pelase? >> > > Using Fvwm 2.6.7 Debian package, doubt it is any of the debian > patches, but I will compile a version without patches and test. > Tested with a fresh compile of Fvwm 2.6.7 without any debian patches, same issue. > > I tested this with other windows and modules. FvwmScript modules > seemed to trigger it, FvwmIdentify did not, so I wonder if it has to > do with transient windows or not (just something I noticed). > Nevermind this, FvwmIdentify is not a traisnent window, the reason it was not producing the warning was it was configured so FvwmIconMan did not create a button for that window. After further testing the warning seems to be due to be caused by adding/removing the button for a window from FvwmIconMan. Windows that appear there trigger the warning but ones that don't appear don't. jaimos
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt 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. > > > I don't get any such messages with or without FvwmIconMan. Can > you give detailed instructions pelase? > Using Fvwm 2.6.7 Debian package, doubt it is any of the debian patches, but I will compile a version without patches and test. Run FvwnIconMan by itself with no configuration, so FvwmIconMan is in its own window (if FvwmIconMan was swallowed in FvwmButtons I did not notice this warning). Once FvwmIconMan is running, run xterm, warning appears, close xterm, warning appears again. I tested this with other windows and modules. FvwmScript modules seemed to trigger it, FvwmIdentify did not, so I wonder if it has to do with transient windows or not (just something I noticed). If you are not able to reproduce this wonder if it is something specific with Debian's xserver, let me know what other output you would want. jaimos
Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
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. I don't get any such messages with or without FvwmIconMan. Can you give detailed instructions pelase? > -- Forwarded message -- > From: Vincent Lefevre > Date: Sun, Dec 25, 2016 at 6:37 PM > Subject: Bug#849355: fvwm: GetWindowSizeHints warnings when windows > and opened and closed > To: Debian Bug Tracking System > > > Package: fvwm > Version: 1:2.6.7-2 > Severity: normal > > I get the following warnings in my .xsession-errors file (where FVWM's > standard error is redirected): > > [fvwm][GetWindowSizeHints]: <> 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. > > when a window is opened. > > [fvwm][GetWindowSizeHints]: <> reason: 4: 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. > > when a window is closed. > > I've tried with windows from the following applications: xterm, Emacs, > xev. This seems to be always reproducible. > > This also occurs when I move to a different page with FvwmPager, with > lots of warnings (I assume one for each window of the old and new > pages). > > After 23 hours, the size of my .xsession-errors file is 678 KB. > I don't think that the space taken is much a problem, but the major > consequence is that these warnings can easily hide more interesting > warning/error messages (from FVWM or applications started by it). > > Edit (from a followup email): > > This only occurs when I use the FvwmIconMan module (which I start > from RestartFunction, itself invoked from InitFunction). > > If I remove my specific FvwmIconMan configuration, the problem still > occurs. > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, > 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages fvwm depends on: > ii libc6 2.24-8 > ii libcairo2 1.14.8-1 > ii libfontconfig1 2.11.0-6.7 > ii libfreetype62.6.3-3+b1 > ii libfribidi0 0.19.7-1 > ii libgdk-pixbuf2.0-0 2.36.2-1 > ii libglib2.0-02.50.2-2 > ii libice6 2:1.0.9-1+b1 > ii libperl4-corelibs-perl 0.003-2 > ii libpng16-16 1.6.26-6 > ii libreadline77.0-1 > ii librplay3 3.3.2-16+b1 > ii librsvg2-2 2.40.16-1 > ii libsm6 2:1.2.2-1+b1 > ii libstroke0 0.5.1-8 > ii libtinfo5 6.0+20161126-1 > ii libx11-62:1.6.4-2 > ii libxcursor1 1:1.1.14-1+b1 > ii libxext62:1.3.3-1 > ii libxft2 2.3.2-1 > ii libxinerama12:1.1.3-1+b1 > ii libxpm4 1:3.5.12-1 > ii libxrender1 1:0.9.10-1 > ii perl5.24.1~rc4-1 > > Versions of packages fvwm recommends: > ii lxmenu-data 0.1.5-1 > ii python 2.7.13-1 > ii python-xdg 0.25-4 > > Versions of packages fvwm suggests: > ii cpp 4:6.2.1-1 > ii libx11-protocol-perl 0.56-7 > ii m41.4.17-5 > ii perl-tk 1:804.033-1+b3 > pn stalonetray > > -- no debconf information > > > Ciao Dominik ^_^ ^_^ -- Dominik Vogt
Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed
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. -- Forwarded message -- From: Vincent Lefevre Date: Sun, Dec 25, 2016 at 6:37 PM Subject: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed To: Debian Bug Tracking System Package: fvwm Version: 1:2.6.7-2 Severity: normal I get the following warnings in my .xsession-errors file (where FVWM's standard error is redirected): [fvwm][GetWindowSizeHints]: <> 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. when a window is opened. [fvwm][GetWindowSizeHints]: <> reason: 4: 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. when a window is closed. I've tried with windows from the following applications: xterm, Emacs, xev. This seems to be always reproducible. This also occurs when I move to a different page with FvwmPager, with lots of warnings (I assume one for each window of the old and new pages). After 23 hours, the size of my .xsession-errors file is 678 KB. I don't think that the space taken is much a problem, but the major consequence is that these warnings can easily hide more interesting warning/error messages (from FVWM or applications started by it). Edit (from a followup email): This only occurs when I use the FvwmIconMan module (which I start from RestartFunction, itself invoked from InitFunction). If I remove my specific FvwmIconMan configuration, the problem still occurs. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fvwm depends on: ii libc6 2.24-8 ii libcairo2 1.14.8-1 ii libfontconfig1 2.11.0-6.7 ii libfreetype62.6.3-3+b1 ii libfribidi0 0.19.7-1 ii libgdk-pixbuf2.0-0 2.36.2-1 ii libglib2.0-02.50.2-2 ii libice6 2:1.0.9-1+b1 ii libperl4-corelibs-perl 0.003-2 ii libpng16-16 1.6.26-6 ii libreadline77.0-1 ii librplay3 3.3.2-16+b1 ii librsvg2-2 2.40.16-1 ii libsm6 2:1.2.2-1+b1 ii libstroke0 0.5.1-8 ii libtinfo5 6.0+20161126-1 ii libx11-62:1.6.4-2 ii libxcursor1 1:1.1.14-1+b1 ii libxext62:1.3.3-1 ii libxft2 2.3.2-1 ii libxinerama12:1.1.3-1+b1 ii libxpm4 1:3.5.12-1 ii libxrender1 1:0.9.10-1 ii perl5.24.1~rc4-1 Versions of packages fvwm recommends: ii lxmenu-data 0.1.5-1 ii python 2.7.13-1 ii python-xdg 0.25-4 Versions of packages fvwm suggests: ii cpp 4:6.2.1-1 ii libx11-protocol-perl 0.56-7 ii m41.4.17-5 ii perl-tk 1:804.033-1+b3 pn stalonetray -- no debconf information
