Description: I imported a picture into my document. I positioned it nicely. I saved the document as docx Later I reloaded it and it wasn't in the correct place or the correct style - bollocks but this particular nuisance occurs all the time with LO and MS formats. However... this time there's more. When I click on the picture and look at it's properties it has become -25,799.00 cm wide (also 119cm tall but that's wrong if the aspect ratio is supposed to be correct). For reference it was 10cm wide before saving. Now this magic number appears to herald some additional buggy behaviour - I can no longer change the size of the figure, what ever I do the properties says it is -25,799.00 cm wide (sometimes the height changes to 0 cm but the image doesn't change). I can only think this is some kind of overflow or maths error. I'm used to LO and docx not playing nicely with figures but this problem takes the piss. FWIW yesterday I was using an older version of LO and while I had the usual wonky reloading of figures this problem did not occur. Today I'm using: Version: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded I'm afraid I don't know the version I was using yesterday (system upgrade) but it was not significantly old. Steps to Reproduce: I don't know if I can reproduce this reliably - it seems to occur at random when saving files to docx format and reloading. If they contain figures it's always a gamble if they will load up in the correct place. Actual Results: Insert figure, save file, reload file and if you're lucky it's in the same place, if you're not luck it isn't and if you're really unlucky the size is -25,799.00 cm Expected Results: Figures are in the correct place and the correct size with the correct wrapping and anchor options Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Version: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Dear ffs, 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
Dear ffs, 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-FollowUp