Hope this is not a duplicate as I can't seem to find anything similar. If I open two windows on the same document in Writer, either on a single monitor or dual monitor set up in both 5.1.3 and the new 5.1.4.2 (and possible earlier versions), I experience problems with page rendering. On the first window on occasion as I type the page 'shakes' back and forth and the cursor is displayed considerably to the right of where it is actually typing. The page itself shifts from the left to the centre of the screen. Also, and possibly related, often reformatting or doing something that causes a reformat, like deleting an image) moves the page location to a different one to the one I am working on (this also happens with the auto save, one minute I am in one part of the document and then the next I am somewhere I was five minutes ago, after autosave has finished). Writer is almost unusable when this happens as the shaking is migraine inducing.. Going to a single window stops the problem and the second window (when on seperate monitor) appears uneffected. I've also noticed the effect is even more problematic when the sidebar is turned off. Here the first screen jumps to a completely different part of the document (so you can't see what you are typing), and the second screen also moves to somewhere else. The document I'm editing is graphics heavy and exhibits another image placement bug, which may or may not relate to this problem. The OS is Windows 7, the graphics card is NVIDIA (750Ti), although this also happened on an AMD card so it probably isn't a driver problem. I have tried with Open GL both disabled and enabled with no change. When using multiple monitors the first monitor is a 1080p wide screen monitor, while the second is an old school 4:3.
One Windows 8 Ent 64-bit en-US with Version: 5.1.4.2 (x64) Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a CPU Threads: 8; OS Version: Windows 6.29; UI Render: GL; Locale: en-US (en_US) so for those not aware, a user is able to "open two windows on the same document in Writer" by selecting the Window -> New Window button from the main toolbar. The two frames share the same document canvas--but the widget controls for the two frames are independent. Believe the document canvas jumps about as its rendering in one frame is recalculated and then applies to the rendering in the other. You can limit this by using the MS Widnows Snap feature (<Windows>+<Left> or <Right> cursors) and allowing the OS to set both frames to the same size. But as Sidebar opens and closes with variable widths the canvas will still be resized in the other frame. Beyond that, don't notice anything too objectionable. Do you have specific STR and perhaps post a redacted sample document that still causes issue. Thanks.
The document is about 31mb so not sure if that is too big to upload? I could certainly take a short film of the behaviour on a camera if not. I'll see if I can take some material out to reduce the size a bit. I'' try and get this up tomorrow. The document also exhibits another bug with image placement, but I've left that now as it can be got around with a bit of editing.
Just an update on this. I think the bug may be caused by the different size of monitor/ window vs the number of pages on display. I have two pages on display on the larger monitor prior to opening the second window. However the second window only has room for one page and the two pages on the main display seem to react and switch to one. The position of the page on the larger monitor switches to the left of the screen and then the problems start. So I think the root of the problem is the number of pages on display variable compared to window size. This seems to be amplified by removing the formatting or side bars. This seems to be reproducable with a new blank document on a single screen. Open a new document, open a new window and have one window full size and the other in a variable size. When you start typing in the full size window you should (hopefully) see the window jerk about the about the place. When it's like this though, removing the formatting/ styles bar actually stops the behaviour, which is slightly different to things in two seperate monitors.
So, in Status bar is the Writer session in "Single Page" mode (the default), or in "Multi-page" mode--and in each Window what is the Zoom setting? Does "jumping" stop if both Windows are at the same scale? On a multi headed Windows 10 Pro system, with Writer in "Single Page" mode, when I use Windows Snap and put both frames onto one monitor and at the same size and the same Zoom--I have almost no "jump" while editing in either frames linkage to the canvas. Inclined to close this out Not A Bug--we're asking LibreOffice VCL/SVX to do things with the document canvas we should not be. But guess it could be seen as need for enhancment for LibreOffice to better manage multiple Window frames in multimonitor configurations of dissimilar resolution. Would be curious to know if folks with multi-headed Linux boxes have any of the same graphic "jump". @Joel, you still set up multi-headed?
Created attachment 125930 [details] Video of 'bug'
I've uploaded a video of the problem in a larger document (hopefully it is clear enough). Closing the formatting side bar causes the cursor to jump to a random document location and stop responding (have to relocate the cursor to the right place again). I had switched the page on the main window to single page only, multiple page doesn't seem to make much change. Jumping does stop if both windows are the same scale, but this would not be the case if like me you have to different sized monitors, where the window sizes are different by necessity. I forgot to mention that I'm using Windows 7.
Looking at the video, can see you are ending up in Multi-page view mode, jumping back and forth to Single-page view mode. I can't reproduce that! A session in Single-page view mode would be centered on the screen. Check the selection in both frames with the document open, down on the status bar.
Setting NEW, but still need reliable STR.
Just checked the settings, one was still on multipage view, but having confirmed both were changed to single page view the problem remains. I should note I both did this with switching from multi page view to single page view and also making sure the single page view was active, saving the document and then restarting so it, loaded in single page view on one screen, then opening new window. I'll have a go at editing this document down to a length I can upload, although I'm pressed for time at the moment so it may not be until next weekend. I've had this occur in a few documents, however (virtually everytime I try and use two windows).
** 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
I can confirm this bug is still present with Libreoffice 6.0.1.1 (sorry for a delayed comeback on this have not had a multi-monitor set up for a while to test properly). I have this occurring again on another computer running a AMD FX APU with Windows 7, and two different brand monitors (one 4:3 and another 16:9, the first running at 70hz refresh, the second at 60hz) acting as a first and second screen. Both monitors and computer are different from when initially reported.
** 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 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
Dear welliben, 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 https://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
Dear welliben, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Issues with dual-page view can be tracked in bug 129827, I added a note there on the kind of flickering you saw. Regarding out-of-sync position and jumps, I think this is all related to differing zoom levels and can safely be consolidated into bug 43253. *** This bug has been marked as a duplicate of bug 43253 ***