Description: LibreOffice freezes when opening attached word document. Steps to Reproduce: 1.Open attached word file in libera office 2. 3. Actual Results: but it is freezing Expected Results: it should open Reproducible: Always User Profile Reset: No Additional Info: no other information
Created attachment 199494 [details] template
Not reproduced in Version: 25.2.0.1.0+ (X86_64) / LibreOffice Community Build ID: 2f6cc65bc813ee5df8c6117deaaf7696c6890372 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Not sure, if this is the same cause as Leela reported the version as 24.8.1, but I bibisected with linux-64-25.8 to 524c266f0f0a3cdccfa9feecfba2a19c9a29b701 tdf#161001 sw floattable: require in-header/footer for non-follow-text-flow
Not reproducible with Version: 24.8.5.2 (X86_64) / LibreOffice Community Build ID: fddf2685c70b461e7832239a0162a77216259f22 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Buovjaga: thanks for the bibisect. Unfortunately the mentioned commit itself was a regression fix, so probably this document was never working properly. The timeline I see is: - f74a6ef94ac957e4c146fc9923d30ce6bd31b5ce (tdf#159453 sw floattable: fix unexpected overlap of in-header fly and body text, 2024-02-13) broke the layout, it was possible for a floating table to jump out of its parent table, which should not happen - 524c266f0f0a3cdccfa9feecfba2a19c9a29b701 (tdf#161001 sw floattable: require in-header/footer for non-follow-text-flow, 2025-01-21) restored this invariant that jumping out of a parent table is not acceptable And the above bugdoc was only "working" in this this timeframe (with serious side-effects), not before and after. By now I think there are some 6 sw floattable bugs like this in the bugzilla. Unfortunately these are far from trivial to fix. I hope to find time to progress with them in the not too distant future. But possibly marking this more important (in terms of severity, priority) than e.g. bug 165029 goes too far.
(In reply to Miklos Vajna from comment #6) > By now I think there are some 6 sw floattable bugs like this in the > bugzilla. Unfortunately these are far from trivial to fix. I hope to find > time to progress with them in the not too distant future. But possibly > marking this more important (in terms of severity, priority) than e.g. bug > 165029 goes too far. Ok, I changed priority and severity for that as well.