Description: 1. When I create a new LibreOffice Writer DOCX file, and set a border space for a paragraph to 0.1 inches, the setting is honored until I save the document as docx and close LO writer. 2. When I open the previously created docx file, the border spacing is not kept and revert back to 0 inches, so every time I close the file I have to set the borders again. 3. This behavior does not happen with ODT files (borders values are properly honored and kept after saving/close operations). 4. This happens on my Debian 11 (linux), 64 bits system, with XFCE DE, not sure if the same goes for Windows systems. Steps to Reproduce: 1. Create a new DOCX file, select a bunch of text and set a border value for all of the sides (top, bottom, left and right) to 0,1 inches. The borders are properly applied. 2. Save the file as DOCX and quit Writer. 3. Open the file and check for the borders value of the text, they are now set to 0 (no borders at all). Actual Results: Borders values already set are missing (not kept), restore back to «0» Expected Results: Borders values already set are kept, after saving/closing docx file. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: es-ES Calc: threaded
Please attach the odt sample file.
Created attachment 190598 [details] File1 is the offending DOCX file
Created attachment 190599 [details] File2 is an ODT file working fine
Created attachment 190600 [details] This how it looks DOCX file file after opening
Created attachment 190601 [details] This how it should render DOCX file file after opening
Created attachment 190622 [details] Screenshot with the style inspector on odt and docx. Seems direct format, it's really different, after save odt as docx. Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8326f1f54b2f4644b52fbfa7106eeeae6e5bb7b CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
I saw a problem on version 6.1 on windows 10
Dear Camaleón, 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
Yet another of those bugs that are «automagically» solved after times goes by :-) I cannot reproduce the bug anymore: Version: 25.8.3.2 (X86_64) Build ID: 8ca8d55c161d602844f5428fa4b58097424e324e CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: es-ES Calc: threaded
Camaleon
Camaleon, for me is NOT working in Version: 25.8.3.1 (X86_64) Build ID: 52ad9dd1c984050a9fb6932dbfb16e86a49e9758 CPU threads: 16; OS: Linux 6.14; UI render: default; VCL: gtk3 Locale: ro-RO (en_US.UTF-8); UI: en-US Calc: threaded I save the odt file on my computer, and save as docx, and the paragraph - border padding is gone.
The same tested with Version: 26.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: f8224b9625c26a7c92a289573765d4a201678d68 CPU threads: 16; OS: Linux 6.14; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
I'm afraid I cannot be of any help here. When trying to check if the bug is reproducible in my testing/devel system running «LibreOfficeDev_26.2.0.0.alpha1», I noticed LO cannot be run. I get this error when running from command line: "oosplash: CPU ISA level is lower than required" Any clue on how to bypass this?
You tested in 25.8.3. How you tested that you said it is fixed?
(In reply to BogdanB from comment #14) > You tested in 25.8.3. How you tested that you said it is fixed? I tested by following the steps I provided in my first comment (#158028), by creating a new LO Writer document, writing down a bunch of text, setting a padding border to 1 cm and saving it as .docx. After closing the docx and opening it again, the padding margin / border is kept, as it should, but cannot test it with LO devel/nightly build version because of the above error that impedes me from opening the application. If you can still reproduce this bug, I'd try with a new / empty LO profile to avoid messing up with some old setting making noise. You can keep this report open and wait for some LO devel takes care of it and asks you to gather further information and/or run additional tests.
Still not working in safe mode. See video
Created attachment 204257 [details] video testing the bug To see the video wight click on it and download, then watch.
I reset also the profile, to safe mode.