Created attachment 125460 [details] Patch forcing NorthWest window gravity X11 window gravity affects how windows are repositioned when their parent is resized. Setting a libreoffice top-level window gravity to something other than NorthWest means that the window will move relative to its parent when the parent is resized. By default, LibreOffice selects StaticGravity, which means that the application window will not move relative to the screen as the parent is resized. So, resizing the window to the right or down works "correctly", but resizing leftwards or upwards moves the application window within the parent, leaving a gap to the left or top of the application window within the frame. Some window managers (metacity) smash the application window geometry to NorthWest so that the application follows the window frame as it should. Others do not adjust this value (xfwm4, twm), and so LibreOffice "breaks" in those environments. That's why this problem doesn't appear on every desktop. I found at least four bug reports about this issue: http://www.linuxquestions.org/questions/linux-desktop-74/strange-libreoffice-problem-on-debian-with-xfce-4175469847/ https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/889212 https://bbs.archlinux.org/viewtopic.php?id=133137 http://forums.debian.net/viewtopic.php?f=6&t=10575 Note that there *is* a useful window gravity value in the WM_NORMAL_HINTS for the application. LibreOffice has a separate parameter for this, and in that case, StaticGravity is a reasonable default as it allows LibreOffice to position toolbars and other contents on the screen without needing to adjust for the window manager frame size. The patch enclosed forces window gravity to NorthWest for all windows in all cases. I can't imagine where this wouldn't be correct, but I haven't reviewed all of the code using this function.
Keith: please send the patch using gerrit: https://wiki.documentfoundation.org/Development/gerrit
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Dear Keith Packard, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I've tested current debian unstable libreoffice, which says 'Version: 6.3.3.2.0+' and things appear to work for me.