Description: Final determination: Setting a row as BOLD causes the save to fail as .UOS. I can select a cell and set it to BOLD and no problem. I can set all the columns BOLD one at a time and no problem. I can select the entire spreadsheet and set it to BOLD and no problem. If I select a row and set it to BOLD, the spreadsheet refuses to save as .UOS. Once a row is set as BOLD, you must UNDO to be able to save. Merely changing it by unselecting BOLD has no positive effect. No other formatting seems to affect the ability to save in .UOS format. Mark Thank you in advance. Steps to Reproduce: 1.select row 2.select BOLD 3.Attempt to "Save" or if changing formats "Save as..." .uos Actual Results: Error saving the document xxxxxxx.uos: Write Error. The file could not be written. Expected Results: Save spreadsheet in .uos format without error. Reproducible: Always User Profile Reset: No Additional Info: Not sure how far back this goes or if it's particular to my system. Ad far back as the release of Linux Mint 21.0 in terms of dates. At least LibreOffice 7.5.0.3 I think, maybe earlier. CPU FX6300 CPU threads: 6; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded System: Kernel: 5.15.0-86-generic x86_64 bits: 64 Compiler: gcc v: 12.3.0 Desktop: Cinnamon 5.8.4 tk: GTK3 3.24.33 (GTK4 4.6.9 available) wm: muffin dm: LightDM 1.30.0 Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy Machine: Type: Desktop Mobo: MSI model: 760GM-P23(FX) (MS-7641) v: 3.0 serial: BIOS: American Megatrends v: 17.17 date: 04/22/2015 Mem: 16Gb DDR3 Video: Nvdia GTS450SC 1Gb - driver version 390.157-0ubuntu0.22.04.2 OS: (up to date) Distributor ID: Linuxmint Description: Linux Mint 21.2 Release: 21.2 Codename: victoria
ask.libreoffice related question: https://ask.libreoffice.org/t/libreoffice-calc-7-5-refuses-to-save-as-unified-office-format-uos/93885
On pc Debian x86-64 with master sources updated today, I could reproduce this. I had this error in console: warn:legacy.osl:244868:244868:xmloff/source/core/SettingsExportHelper.cxx:176: this type is not implemented now runtime error: file file:///home/julien/lo/libreoffice/instdir/program/../share/xslt/export/uof/odf2uof_spreadsheet.xsl line 1122 element value-of xsltApplySequenceConstructor: A potential infinite template recursion was detected. You can adjust xsltMaxDepth (--maxdepth) in order to raise the maximum number of nested template calls and variables/params (currently set to 3000). For the test I unzipped a simple ods file containing test in 2 cells, then I select the row and put it bold. I noticed this in content.xml: <style:style style:name="ce1" style:family="table-cell" style:parent-style-name="Default"> ... <table:table-column table:style-name="co1" table:number-columns-repeated="16384" table:default-cell-style-name="ce1" /> Workaround: select just the range of cells you want to put bold. xslt files is a PITA to maintain and should be replaced by C++ conversion.
In addition to Julien: increasing xsltMaxDepth to 30000, and xsltMaxVars to 40000 results in memory allocation problems in libxslt; smaller values do not succeed (the defaults are 3000 and 15000, resp.). The change can be done in XSLT::Reader::execute, before the call to xsltNewTransformContext. If someone has energy and knowledge, one could try to change the respective XSLT: filter/source/xslt/export/uof/odf2uof_spreadsheet.xsl; maybe there's a way to change the recursive handling of repeated columns into some loop or something.
Dear Mark Farrell, 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