This bug was filed from the crash reporting server and is br-fbe0f467-75a7-4b50-96e2-ed9db71efd6e. ========================================= Steps processed: Open Excel -> menue "insert" -> object -> from tab "create new" select "OpenDocument spreadsheet" -> LibreOffice crashes
I supposed you meant "LO Calc" instead of "Excel". For the rest, I don't see "from tab "create new"" On Calc if I click Insert/Object, I've got 3 choices: - Formula... - QR Code... - OLE Object...
I meant what I wrote: - start Microsoft Excel of Microsoft 365 - insert object - create new - select "OpenDocument spreadsheet" - LibreOffice is starting in the background and 1 second later crashing - Microsoft Excel returns a message like "Not possible to open source application with the enbedded object" I'm a user not a software developer.
[Automated Action] NeedInfo-To-Unconfirmed
Hello Silvio, 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.
Tested same steps with LibreOffice 7.1.4.2. Result: LibreOffice is not crashing. A new MS Excel error message pops up: "the source application of the embedded object cannot be started" Version: 7.1.4.2 (x64) / LibreOffice Community Build ID: a529a4fab45b75fefc5b6226684193eb000654f6 CPU threads: 16; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-CH (de_CH); UI: de-DE Calc: CL
(In reply to silvio from comment #5) > Tested same steps with LibreOffice 7.1.4.2. > > Result: LibreOffice is not crashing. > A new MS Excel error message pops up: > "the source application of the embedded object cannot be started" > > > Version: 7.1.4.2 (x64) / LibreOffice Community > Build ID: a529a4fab45b75fefc5b6226684193eb000654f6 > CPU threads: 16; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: > win > Locale: de-CH (de_CH); UI: de-DE > Calc: CL I confirm the problem, but I'm not sure it's the LibreOffice's problem. Mike, could you please look at it and give us your opinion. Thanks
I didn't debug it; yet, I am sure it's LibreOffice's fault. I don't believe that we can really assume our COM implementation to be reliable enough to assume it's MS fault - we should assume the opposite, until proven wrong ;) The debugging requires registering the debug build's COM server in system (e.g., building the MSI package, and installing it with WRITE_REGISTRY=1, making sure to uninstall normal LibreOffice (and OpenOffice) installation to avoid conflicts); changing DllMain in embedserv/source/inprocserv/dllentry.cxx to have some infinite loop like "static volatile int i = 1; while (i);" to allow attaching debugger (or maybe just attaching the debugger to Excel, and putting a breakpoint to the function); and then starting the problematic sequence.
Set to NEW by Comment 7
Dear silvio, 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
Created attachment 202417 [details] Bug 138032 - attachment 2025-08-20
Dear QA Team I've tested with the newest LibreOffice version: Version: 25.8.0.4 (X86_64) Build ID: 48f00303701489684e67c38c28aff00cd5929e67 CPU threads: 16; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Raster; VCL: win Locale: de-CH (de_CH); UI: de-DE Calc: CL threaded Similar to my comment 2 from 2020-11-06 23:09:20 UTC I did: 1) start Microsoft Excel of Microsoft 365 2) insert -> object 3) create new: 4) select "OpenDocument spreadsheet" 5) after 4 seconds Excel is blocked (Windows cursor is spinning) and 2 LibreOffice tasks appear in the windows task manager: -> see screenshot A) in attached document 6) after ca. 1 minute 30 seconds an Excel message appears: -> see screenshot B) in attached document 7) click on button "OK" (not "cancel") leads to a new Excel message after a few seconds: -> see screenshot C) in attached document 8) click on button "OK" and Excel is available again and nothing happens. Only 1 LibreOffice task is active in the windows task manager and disappears after a few minutes: -> see screenshot D) in attached document Best regards Silvio