Bug 141246 - Blue screen when trying to open a file .ods
Summary: Blue screen when trying to open a file .ods
Status: RESOLVED DUPLICATE of bug 140952
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-25 11:10 UTC by Wilhelm Petersen
Modified: 2021-03-25 17:41 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
foto of the blue screen, file that causes it (51.82 KB, application/vnd.oasis.opendocument.spreadsheet)
2021-03-25 11:10 UTC, Wilhelm Petersen 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wilhelm Petersen 2021-03-25 11:10:24 UTC 
Created attachment 170735 [details]
foto of the blue screen, file that causes it

when doubleclicking the file 'bilderliste.ods' a blue screen follows, see picture.

ThinkPad T470s, RAM: 16GB
Windows 10 Pro, version 20H2
Comment 1 Wilhelm Petersen 2021-03-25 13:42:43 UTC 
trying to open on an older PC with LibreOffice Version: 6.2.0.3 (x64) works fine.
Comment 2 [REDACTED] 2021-03-25 13:51:11 UTC 
From .ODS attachement:

 <config:config-item config:name="PrinterName" config:type="string">\\MB1\Kyocera FS-9130DN KX</config:config-item>

=> Kyocera printer 

This is most likely caused by Windows update of 2021-03-09 (KB5000802) and hence a duplicate of tdf#140952. 

See also: https://support.microsoft.com/en-us/topic/march-15-2021-kb5001567-os-builds-19041-868-and-19042-868-out-of-band-6e0844a2-7551-4b2d-9c4b-4274a5949bf3

Solution: 
Windows -> Settings -> Update & Security and install latest patches (at least optional Patch KB5001567). 

Feel free to reopen, if the conclusion is not correct for you.

*** This bug has been marked as a duplicate of bug 140952 ***
Comment 3 Wilhelm Petersen 2021-03-25 15:11:54 UTC 
Thanks to Frank

having updated to KB5001649 today it works again
Comment 4 [REDACTED] 2021-03-25 17:41:59 UTC 
(In reply to Wilhelm Petersen from comment #3)
> Thanks to Frank

Whoever Frank is ;-)