Bug 155111 - LibreOffice won't start after upgrading on Windows 11
Summary: LibreOffice won't start after upgrading on Windows 11
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-01 16:37 UTC by Rolf Suessbrich
Modified: 2023-06-28 19:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
one of the windows dump files (23.50 KB, application/octet-stream)
2023-05-01 17:14 UTC, Rolf Suessbrich
Details
irregular output using the --help parameter while starting soffice (293.65 KB, image/png)
2023-05-02 09:04 UTC, Rolf Suessbrich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Suessbrich 2023-05-01 16:37:57 UTC
Description:
Out of the blue LO refuses to start. It occurred first yesterday for 7.5.2.2. I've deinstalled this version und reinstalled 7.4.6.2, but ist is tha same. Finally I've downloaded 7.6.0.0nut alas, it ps the same behaviour.

Steps to Reproduce:
1. Pressing the Start button OR statig it via CMD-Windows
2.
3.

Actual Results:
It does not work nor is the internal crash handling activated. What works is starting from Explorer soffice_safe.exe either by double click or by drawing this into a command window. The safe-version seems to run sufficiently.
I have tried all options available in the safe-mode, e. g. resetting to factory defaults and so on, no result.

Expected Results:
as explained


Reproducible: Always


User Profile Reset: Yes

Additional Info:
In the Event-Logs there is an entry for each crash:

Name der fehlerhaften Anwendung: soffice.bin, Version: 7.6.0.0, Zeitstempel: 0x644f2560
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.22621.1555, Zeitstempel: 0x235a45d0
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x000000000006fd1f
ID des fehlerhaften Prozesses: 0x0xA30
Startzeit der fehlerhaften Anwendung: 0x0x1D97C4530A19759
Pfad der fehlerhaften Anwendung: C:\Program Files\LibreOfficeDev 7\program\soffice.bin
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: 914915c1-0173-43a2-9220-52d1f00767db
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

-- or ---

Name der fehlerhaften Anwendung: soffice.bin, Version: 7.4.6.2, Zeitstempel: 0x6402696f
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.22621.1555, Zeitstempel: 0x235a45d0
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x000000000006fd1f
ID des fehlerhaften Prozesses: 0x0x345C
Startzeit der fehlerhaften Anwendung: 0x0x1D97C3F0886B6A5
Pfad der fehlerhaften Anwendung: C:\Programme\LibreOffice\program\soffice.bin
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: cac3c983-f15a-430e-8c1f-38011930b333
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

-------------------

Version: 7.4.6.2 (x64) / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: default; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded
Comment 1 Rolf Suessbrich 2023-05-01 17:14:11 UTC
Created attachment 187034 [details]
one of the windows dump files
Comment 2 Rolf Suessbrich 2023-05-02 09:04:00 UTC
Created attachment 187045 [details]
irregular output using the --help parameter while starting soffice
Comment 3 Rolf Suessbrich 2023-05-02 09:18:07 UTC
Strange!

This morning after restarting the PC the problem still exixts.

I've started to find any useful additional information. The only quirky issue is the output starting soffice.exe in a cmd-window with the parameter --help. After a while a new window is presented which contains only the last part of the messages, see attached screenprint. It is possible to see in sysinternals process-explorer that this new terminal window is launched by soffice.bin. 

I looked at all entries in the registry referring LibreOffice but none of the numerous entries found seemed to be irregular. 

Finally, I started LIBO again by double clicking the icon and 7.4.6.2 started as expected. Oh wonder! Such the problem is currently no longer reproducible.
Comment 4 Rolf Suessbrich 2023-05-05 15:41:44 UTC
In the meantime 7.5.2.2 works also correctly here. No issues with launching LIBO in this release.

It came to my mind what might be the reason for observed problems: The number of processed files was growing and growing and might have reached well above 100 files. I don't know if LIBO performs any housekeeping there in file registrymodifications.xcu. Since I have deleted the full path C:\Users\rolf\AppData\Roaming\LibreOffice\4\ I have no chance to look further on this issue.
Comment 5 Stéphane Guillou (stragu) 2023-05-11 15:48:24 UTC
Thank you for the report and the detailed testing, Rolf.
As you can't reproduce anymore with a new profile, I'll close as "works for me", but please set back to "unconfirmed" if it reappears and you can provide more information.
Thank you!
Comment 6 Rolf Suessbrich 2023-06-06 09:45:24 UTC
On another new PC the problem reappeared: After upgrading a runnung Version of 7.4.6 to 7.5.3 LIBO didn't start any more.

After download of the installation file for 7.5.3 and starting the installation the usual question popped up, if the existing installation should be removed. This was accepted. After the installation pressing the newly allocated button for LIBO on the screen nothing happend!
So we completely removed the existing 7.5.3 installation using System Control > Programs and Features. An Reboot was done and after that the installation of LIBO was repeated.

The result: 7.5.3 now starts without any problems.