Bug 144736 - LO 7.1.6.x does not run on Windows 10 or 8.1, it just crashes
Summary: LO 7.1.6.x does not run on Windows 10 or 8.1, it just crashes
Status: RESOLVED DUPLICATE of bug 144598
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.1.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-26 17:08 UTC by clay0
Modified: 2021-09-27 23:06 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description clay0 2021-09-26 17:08:41 UTC
Description:
LO 7.1.6.x crashes every time you try to run it on Windows.
Operating systems: Windows 10 64-bit and Windows 8.1 64-bit
Installers used:
· LibreOffice_7.1.6.1_Win_x86.msi
· LibreOffice_7.1.6.2_Win_x86.msi
· LibreOffice_7.1.6.1_Win_x64.msi
· LibreOffice_7.1.6.2_Win_x64.msi
· LibreOfficePortablePrevious_7.1.6_MultilingualStandard.paf.exe

Steps to Reproduce:
1.Use any of the above installers.
2.Then try to run LO 7.1.6.x.
3.That's it.

Actual Results:
LO 7.1.6.x crashes every time you try to run it on Windows 10 64-bit or Windows 8.1 64-bit.

Expected Results:
LO 7.1.6.x should not crash every time you try to run it on Windows 10 64-bit or Windows 8.1 64-bit.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
(User profile deleted multiple times.)
According to the Windows problem reports the crashing module is always "skialo.dll".
No crashes at all with LO <= 7.1.5 or with LO 7.2.x.
(Also no crashes with LO 7.1.6 on Linux.)

Since it's impossible to open LO 7.1.6.x on Windows it's also impossible to access "About LibreOffice". The following information is from one of the problem reports:

       Problem signature
Problem Event Name:	APPCRASH
Application Name:	soffice.bin
Application Version:	7.1.6.2
Application Timestamp:	61371082
Fault Module Name:	skialo.dll
Fault Module Version:	7.1.6.2
Fault Module Timestamp:	6136515e
Exception Code:	        c000001d
Exception Offset:	004c67a3
Operating system:	10.0.19043.2.0.0.256.48
Comment 1 Julien Nabet 2021-09-26 17:29:41 UTC
It may be a dup of tdf#144598 fixed from 7.1.7.
Please try https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28Skia.29

If your pb is fixed with this part specifically:
"
Open registrymodifications.xcu in a plain text editor, and search for UseSkia text string there.

    If found, replace true with false in that line.
    If not found, add this line to the file before the final </oor:items>:"
It's a dup.
Comment 2 clay0 2021-09-26 20:05:30 UTC
(In reply to Julien Nabet from comment #1)
> It may be a dup of tdf#144598 fixed from 7.1.7.
> Please try
> https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.
> 28Skia.29
> 
> If your pb is fixed with this part specifically:
> "
> Open registrymodifications.xcu in a plain text editor, and search for
> UseSkia text string there.
> 
>     If found, replace true with false in that line.
>     If not found, add this line to the file before the final </oor:items>:"
> It's a dup.

Thank you! In "registrymodifications.xcu" I added the line "<item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="UseSkia" oor:op="fuse"><value>false</value></prop></item>" before the final "</oor:items>" and LO 7.1.6 does not crash anymore.

      skia.log
RenderMethod: raster
Compiler: Clang

      About LibreOffice
Version: 7.1.6.2 (x86) / LibreOffice Community
Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: CL
Comment 3 Julien Nabet 2021-09-26 20:08:15 UTC
Thank you for your feedback.
So it's a dup of tdf#144598 which is fixed from 7.1.7 (for 7.1 branch) or 7.2.2 (for 7.2 branch)

*** This bug has been marked as a duplicate of bug 144598 ***
Comment 4 clay0 2021-09-26 20:22:53 UTC
(In reply to Julien Nabet from comment #3)
> Thank you for your feedback.
> So it's a dup of tdf#144598 which is fixed from 7.1.7 (for 7.1 branch) or
> 7.2.2 (for 7.2 branch)
> 
> *** This bug has been marked as a duplicate of bug 144598 ***

From 7.2.2 for the 7.2 branch? No crashes here for 7.2.0.4 or for 7.2.1.2.
Comment 5 Julien Nabet 2021-09-27 18:29:42 UTC
Ok so let's rather put WFM then since there's no fix spotted for this one if it's not a dup of tdf#144598
Comment 6 Ming Hua 2021-09-27 19:04:51 UTC
(In reply to clay0 from comment #4)
> (In reply to Julien Nabet from comment #3)
> > So it's a dup of tdf#144598 which is fixed from 7.1.7 (for 7.1 branch) or
> > 7.2.2 (for 7.2 branch)
> 
> From 7.2.2 for the 7.2 branch? No crashes here for 7.2.0.4 or for 7.2.1.2.
That bug is non-deterministic, meaning that it randomly appear during the build process.  All the source code prior to, and including 7.1.6 version has this bug, but it seems only in the 7.1.6 build process this bug was triggered and resulted in a problematic binary application program (and installer).

The fix in 7.1.7 and 7.2.2 means that bug will definitely not appear anymore, it doesn't mean all builds before the fix will have the "can't start with Skia" problem.

(In reply to Julien Nabet from comment #5)
> Ok so let's rather put WFM then since there's no fix spotted for this one if
> it's not a dup of tdf#144598
Not that it's very important, but I still believe this should be a dup of 144598, since according to bug 144174, 7.2.1 final release is alright (https://bugs.documentfoundation.org/show_bug.cgi?id=144174#c12), only 7.2.1 RC1 has the problem.
Comment 7 mike.a.nicolay 2021-09-27 19:51:25 UTC
So, to get the LibreOffice to work (to even start working) on Windows10 I have to become an IT Specialist?
Not a very practical solution! It seems that the TOOL, itself, is now more important than what the tool was made to do!
I just wanted a Word Processor, I didn't want to have to learn how to build one.
Comment 8 V Stuart Foote 2021-09-27 23:06:45 UTC
dupe to 144598 for tracking...

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