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