Bug 144679 - LibreOffice crashes at startup after fresh install
Summary: LibreOffice crashes at startup after fresh install
Status: RESOLVED DUPLICATE of bug 144598
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Keywords: wantBacktrace
Depends on:
Reported: 2021-09-23 10:06 UTC by martin.j.lisowski
Modified: 2021-09-24 19:21 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

user profile (ZIPed) (27.06 KB, application/octet-stream)
2021-09-23 10:08 UTC, martin.j.lisowski
Windows Crash Report file (20.75 KB, text/plain)
2021-09-23 10:11 UTC, martin.j.lisowski

Note You need to log in before you can comment on or make changes to this bug.
Description martin.j.lisowski 2021-09-23 10:06:45 UTC
With a fresh install of LibreOffice on Windows 10 Home the LibreOffice starter application and also the Writer, Calc, Impress, Base, Draw, Math components immediately crash on startup (application window or splash screen never shows).
Only starting in safe mode works. The typical repair options in safe mode don't work. LibreOffice only works in safe mode.
LibreOffice install choice was "Typical" without pre-loading starter.

Steps to Reproduce:
1. Fresh ("Typical") install of Libreoffice on Windows 10 Home 21H1 (German) 
2. Attempt to start "LibreOffice" application
3. Application crashes (briefly visible in Task Manager, Windows Event Log has details)

Actual Results:
The application window never opens. Only brief flash of mouse pointer. Two LibreOffice processes briefly visible in Windows Task Manager. Windows Event Log shows 3 entries (2x Error, 1x Info) - pasted in Other Information.

Expected Results:
LibreOffice application window should have shown.

Reproducible: Always

User Profile Reset: Yes

Additional Info:
LibreOffice does start in safe mode.
However, none of the typical remedies resolve the original problem:
1) Disabling hardware acceleration does not help
2) resetting user profiles does not help (as expected, since it's a fresh user profile)
3) reset to factory defaults does not help (it's fresh install)

|Edition|Windows 10 Home|
|Installiert am|‎01.‎07.‎2021|
|Leistung|Windows Feature Experience Pack 120.2212.3530.0|

Version: (x64) / LibreOffice Community
Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3
CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: default; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded

Windows Event Log (Application Log):

Name der fehlerhaften Anwendung: soffice.bin, Version:, Zeitstempel: 0x6135e2a5
Name des fehlerhaften Moduls: skialo.dll, Version:, Zeitstempel: 0x61353cf8
Ausnahmecode: 0xc000001d
Fehleroffset: 0x000000000052b9c0
ID des fehlerhaften Prozesses: 0x2df4
Startzeit der fehlerhaften Anwendung: 0x01d7b05b37bc6a3f
Pfad der fehlerhaften Anwendung: C:\Program Files\LibreOffice\program\soffice.bin
Pfad des fehlerhaften Moduls: C:\Program Files\LibreOffice\program\skialo.dll
Berichtskennung: 392e0e97-4be0-4620-bb42-190dc95e4a4a
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 


Aus einem der folgenden Gründe kann Windows nicht auf die Datei "" zugreifen: Es besteht ein Problem mit der Netzwerkverbindung, dem Datenträger mit der gespeicherten Datei bzw. den auf dem Computer installierten Speichertreibern, oder der Datenträger fehlt. Das Programm LibreOffice wurde von Windows wegen dieses Fehlers geschlossen.

Programm: LibreOffice

Der Fehlerwert ist im Abschnitt "Zusätzliche Dateien" aufgelistet.
User action
1. Öffnen Sie die Datei erneut. Diese Situation ist eventuell ein temporäres Problem, das selbstständig behoben wird, wenn das Programm erneut ausgeführt wird.
2. Wenn Sie weiterhin nicht auf die Datei zugreifen können und
	- diese sich im Netzwerk befindet,  dann sollte der Netzwerkadministrator sicherstellen, dass kein Netzwerkproblem besteht und dass eine Verbindung mit dem Server hergestellt werden kann.
	- diese sich auf einem Wechseldatenträger, wie z. B. einer Diskette oder einer CD, befindet, überprüfen Sie, ob der Datenträger richtig in den Computer eingelegt ist.
3. Überprüfen und reparieren Sie das Dateisystem, indem Sie CHKDSK ausführen. Klicken Sie dazu im Startmenü auf "Ausführen", geben Sie CMD ein, und klicken Sie auf "OK". Geben Sie an der Eingabeaufforderung CHKDSK /F ein, und drücken Sie die EINGABETASTE.
4. Stellen Sie die Datei von einer Sicherungskopie wieder her, wenn das Problem weiterhin besteht.
5. Überprüfen Sie, ob andere Dateien auf demselben Datenträger geöffnet werden können. Falls dies nicht möglich ist, ist der Datenträger eventuell beschädigt.  Wenden Sie sich an den Administrator oder den Hersteller der Computerhardware, um weitere Unterstützung zu erhalten, wenn es sich um eine Festplatte handelt.

Zusätzliche Daten
Fehlerwert: 00000000
Datenträgertyp: 0


Fehlerbucket 1816975287134667208, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

P1: soffice.bin
P3: 6135e2a5
P4: skialo.dll
P6: 61353cf8
P7: c000001d
P8: 000000000052b9c0

Angefügte Dateien:

Diese Dateien befinden sich möglicherweise hier:

Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 392e0e97-4be0-4620-bb42-190dc95e4a4a
Berichtstatus: 268435456
Bucket mit Hash: d2368d4c5b572205b93731659b5341c8
CAB-Datei-Guid: 0


WER Log:

Faulting Application Path:	 C:\Program Files\LibreOffice\program\soffice.bin
Creation Time:			 23.09.2021 11:13:09
Problem:			 Nicht mehr funktionsfähig
Status:				 Bericht gesendet

Problem signature
Problem Event Name:           APPCRASH
Anwendungsname:               soffice.bin
Anwendungszeitstempel:        6135e2a5
Fehlermodulname:              skialo.dll
Fehlermodulzeitstempel:       61353cf8
Ausnahmecode:                 c000001d
Ausnahmeoffset:               000000000052b9c0

Extra information about the problem
Bucket ID:			 d2368d4c5b572205b93731659b5341c8 (1816975287134667208)
Comment 1 martin.j.lisowski 2021-09-23 10:08:30 UTC
Created attachment 175211 [details]
user profile (ZIPed)
Comment 2 martin.j.lisowski 2021-09-23 10:11:36 UTC
Created attachment 175212 [details]
Windows Crash Report file
Comment 3 Ming Hua 2021-09-23 10:38:47 UTC
Please have a look at bug 144598, I suspect this is the same issue.
Comment 4 Julien Nabet 2021-09-23 11:22:45 UTC
Do you use any accessibility tool? If yes, could you disable them temporarily and give it a try?
Did you install any specific fonts? If yes, could you uninstall them temporarily and give it a try?

Would it be possible you attach a backtrace by following https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace ?
Comment 5 Julien Nabet 2021-09-23 11:25:31 UTC
Also, could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28Skia.29 ?
Comment 6 martin.j.lisowski 2021-09-23 13:19:27 UTC
I didn't (consciously) install any additional fonts (fresh Windows install about 3 months ago).

What exactly do you mean by "accessibility tool"? Do you mean input devices? I have USB keyboard & mouse, USB headset, USB gaming keyboard (disconnected) and webcam (disconnected).

I have MS Visual Studio 2019 installed - would that help to generate the needed backtrace? If possible I'd prefer to not installed another SDK on top of Visual Studio. Pls advise. Manually attaching to process doesn't work because it crashes so fast.

I had a 1 year old video driver installed. Updated to most recent NVIDIA 472.12 and bug still persists.

Re SKIA: In Help->About (when started in safe mode) I currently have "UI render: default; VCL: win" - no mention of SKIA, hence the rest not applicable according to the page you linked
Comment 7 Julien Nabet 2021-09-23 16:48:51 UTC
Ok so not SKIA related.

For backtrace, I don't know if Visual Studio 2019 helps, perhaps it depends on the modules you installed, anyway you need above all Windbg as indicated in the link.

Concerning accessibility, I mean specific zoom, high contrast, computer screen reader, etc.
Comment 8 Ming Hua 2021-09-23 16:58:10 UTC
(In reply to Julien Nabet from comment #7)
> Ok so not SKIA related.
I wouldn't be so sure.  The crash report file (attachment 175212 [details]) clearly says:

P1: soffice.bin
P3: 6135e2a5
P4: skialo.dll

I still think this is a duplicate of bug 144598.  I don't know what exactly Safe Mode does, but I think the reporter can try manually editing the user profile as https://bugs.documentfoundation.org/show_bug.cgi?id=144598#c2 said, in order to rule out Skia definitely.
Comment 9 Julien Nabet 2021-09-23 18:29:10 UTC
(In reply to Ming Hua from comment #8)
> (In reply to Julien Nabet from comment #7)
> > Ok so not SKIA related.
> I wouldn't be so sure.  The crash report file (attachment 175212 [details])
> clearly says:
> Problemsignatur:
> P1: soffice.bin
> P2:
> P3: 6135e2a5
> P4: skialo.dll
> ...

Martin, did you apply https://bugs.documentfoundation.org/show_bug.cgi?id=144598#c2 ?
Comment 10 martin.j.lisowski 2021-09-23 19:32:18 UTC
I report partial success:

I appended
<item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="UseSkia" oor:op="fuse"><value>false</value></prop></item>

to the registrymodifications.xcu

and now Libreoffice application and all the components start up!
Comment 11 Julien Nabet 2021-09-23 19:38:48 UTC
Thank you for your feedback, Ming was right.
Let's put this one as DUP.

*** This bug has been marked as a duplicate of bug 144598 ***
Comment 12 martin.j.lisowski 2021-09-23 19:44:47 UTC
Ok, thanks Julien and Ming for the quick help! Really appreciated

Comment 13 Julien Nabet 2021-09-23 19:47:02 UTC
Thanks to the workaround, you don't encounter the pb but it's not FIXED, it's a DUP of another bugtracker.

*** This bug has been marked as a duplicate of bug 144598 ***
Comment 14 martin.j.lisowski 2021-09-23 20:06:47 UTC
Just looked at the comments of Bug 144598 - for the record my hardware is
CPU Intel i7 980X (so no AVX!)
Comment 15 Julien Nabet 2021-09-24 19:11:28 UTC
Martin: good point

Mike/Luboš: since advice https://bugs.documentfoundation.org/show_bug.cgi?id=144598#c2 worked for Martin but his CPU (Intel i7 980X) doesn't use AVX, do you think there's another bug here with Skia Raster or did I miss something?
Comment 16 Mike Kaganski 2021-09-24 19:17:46 UTC
(In reply to Julien Nabet from comment #15)

The bug was exactly that there were AVX (or any other new) instructions compiled in the code, that were attempted to execute on CPUs *without* support for that instruction set, causing that *older* CPU to crash the process. Luboš made sure that the code that is intended to be executed on all supported systems is built strictly using SSE2 instruction set.

What comment 14 mentions fits that perfectly. If Martin's system had AVX support, it would have no problem running LO in the first place.
Comment 17 Julien Nabet 2021-09-24 19:21:44 UTC
Thank you Mike for the explanation. I had thought that the pb was for CPUs which support AVX but it was the contrary.
So it's indeed a dup of tdf#144598.

*** This bug has been marked as a duplicate of bug 144598 ***