BUG 1) LO Writer forgets how items are stacked upon another after reopening of a document. It forgets the order of sorting if there are two or three SVGs laying upon another (or a text frame on a SVG image) and are sorted by "send to back" and "send to front". Sometimes when opening a documents it is OK, oftentimes it is messed up. LO does not remember how they were put. This messes up the design of a document and one cannot trust LO Writer. This bug happens often, after inserting additional SVGs on other pages of the document, then closing the document and open it again. BUG 2) I write several Writer documents including SVG files. Then I put them together by "manual page break", so they are in one document but separate from each other. Sadly this is in LO Writer only theoretically. If I edit one document in the middle of the put together document, and the text exceeds over the end of that document, SVGs in the following documents disappear until I reopen the whole document. BUG 3) You have a main Writer document. When adding (by manual page break) a second document that includes SVGs, those SVGs are not imported. You have to manually place them from the second document to the main document. JPG images are also not imported. BUG 4) If you have a JPG image and use the context menu command to add a description, it creates a frame around the picture, but the image doesn’t sit exactly on top of the frame bit 1 millimetre below. The created text has huge spacing, but using the paragraph command and make the line spacing 80 or 90 % proportional messes up the placing of the image, some parts disappear. BUG 5) When proportionally reducing "line width" of a paragraph (for example to 90 %) the first and second line move closer together than the others. If further reducing line width this effect becomes more severe. BUG 6) When I copy parts of a Writer document (text, image, SVG) by pressing CMD-C (on OSX) Writer oftentimes (in three out of four cases) inserts at this place a bookmark. BUG 7) In full-screen mode it is possible to edit a Writer document, but it is impossible to save it. CMD-S (on OSX) doesn’t work. BUG 8) Moving selected text from a Writer document to the OSX desktop (called Finder) deletes the text from the Writer document. Expected behaviour is simply to place a Text-Clip on the desktop with the text in the Writer document unaltered (as any text application in OSX does). BUG 9) LO 5.3 seems to have changed the font-rendering. All fonts in sizes of 12 point or lower (the usual size for editing documents) have terrible spacing, letters move/smear into another, spaces disappear. With this major bug I’m stuck with LO 5.2.7.2. Designing a newsletter in WYSIWYG is now impossible. Finally: I always have to triple check, if there are missing SVGs and messed up designs, when I am opening a Writer document. I don’t do anything exotic, but LO is quite buggy for serious use. Meanwhile I know how to work around all those bugs, but it costs time. LO 5.2.7.2 and older
@DeepFlight5 : Please file separate bug reports for each issue you are experiencing. When doing so, it would be helpful if you could check to see whether your bug has already been reported first - the bug submission assistant will make suggestions in this regard whilst you are typing the title of your bug. Additionally, please also either provide a sample document in which you experience the problem, with instructions on how to reproduce the buggy behaviour, or a series of step by step instructions on how to see the bug. Thank you for your assistance in this, it makes our volunteer QA triaging job easier and benefits all in the long run.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180102
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180129