Description: After installing the latest version from the Pre-releases server for Windows, whenever I open a DOCX file from the Recent Documents list, Libreoffice crashes. This happens after I switch the UI to Tabbed instead of the Standard Toolbar UI. On Standard Toolbar UI or when creating a document anew the program doesn't crash. I have tried resetting the software in Safe Mode, but it makes no difference and still crashes whenever I do as above. Steps to Reproduce: 1. Install LibreOffice 25.8.0.4 from the Pre-releases server 2. Open a random DOCX document or one stored in the Recent Documents list within Libreoffice 3. Change the User Interface from Standard Toolbar to Tabbed and "Apply to All" Actual Results: While the change to Tabbed UI works as expected when I have not opened any document, i.e. with an empty document, repeating the same procedure with an actual DOCX file open in Libreoffice will crash the program. Expected Results: No crash when using Tabbed as default UI. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 25.8.0.4 (X86_64) Build ID: 48f00303701489684e67c38c28aff00cd5929e67 CPU threads: 12; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Created attachment 202356 [details] Crash dump after Tabbed UI change
Maybe a duplicate of tdf#141073
(In reply to m_a_riosv from comment #2) > Maybe a duplicate of tdf#141073 FYI the crashes only started happening on two different computers right after I upgraded my stable LibreOffice 25.2 to 25.8, which actually hasn't been officially released yet. No such issue with 25.2.
Maybe I'm not following right the steps, but no crash with Version: 25.8.1.0.0+ (X86_64) / LibreOffice Community Build ID: 00b2dd5faeb43ff50c84139a31892956a6a142d7 CPU threads: 16; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Thanks for reporting this issue. It looks like a duplicated of bug 167956 *** This bug has been marked as a duplicate of bug 167956 ***