I have been using Libre Office v. 6.4.7 and it has been great to work with - Thank You. I updated to v.7.0.4 and when I start the program my monitor stops working and goes into hibernate, the computer keeps running. I have to do a hard stop (hold on/off button down) to reboot computer. All seems well after reboot but if I try Libre Office again I get the same results. Device name AsusDesktop Processor AMD A10-7800 Radeon R7, 12 Compute Cores 4C+8G 3.50 GHz Installed RAM 8.00 GB (6.94 GB usable) Device ID 13A7496C- Product ID 00326-10000-00000-AA218 System type 64-bit operating system, x64-based processor Pen and touch No pen or touch input is available for this display Edition Windows 10 Home Version 20H2 Installed on 9/1/2020 OS build 19042.685 Experience Windows Feature Experience Pack 120.2212.551.0 I am going to reload v.6.4.7 to get Libre Office running again. Thanks for your efforts and just wanted to let you know of the problem for your reference.
Hi. I can not reproduce the bug in: Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: threaded and Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 8df14a82cee4fe0c4ca6f994c7c3f92373b411a3 CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: threaded
Hi. I also can not reproduce the bug in: Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: threaded and Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: c950dedc9b6a9306e83491c6e895c0ceee11ba8a CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: threaded
srroberti: in your Windows start menu there should be an entry to start LibreOffice in safe mode. You could try that with 7.0.4. I suspect the weird behaviour is somehow linked to the new Skia graphics engine.