https://bugs.documentfoundation.org/show_bug.cgi?id=151907

            Bug ID: 151907
           Summary: Brand new Computer; Writer Crashes needs to turn off
                    hardware acceleration to not crash
           Product: LibreOffice
           Version: 7.3.7.2 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: minor
          Priority: medium
         Component: LibreOffice
          Assignee: [email protected]
          Reporter: [email protected]

Description:
Bought a brand new HP Omen laptop (Model N0797Nnr, AMD Ryzen 7 6800H,
Windows11, Nvidia GeforceRTX 3060 6GB) Installed fresh LibreOffice 7.3.7.2
(x64).
Open Launcher, select create Writer Document. Writer Document opens and
immediately crashes.
In safe mode, Configure>Disable hardware acceleration (OpenGL, OpenCL, Vulkan);
then Writer works.

Steps to Reproduce:
1.Open Launcher
2.Open Create new Writer Document
3.Writer Document app opens and immediately crashes, no error code or window

Actual Results:
Writer is not usable if it crashes immediately.
Workaround:
1. Start in "Safe Mode" then;
2. Select "Configure" and CHECK "Disable hardware acceleration (OpenGL, OpenCL,
Vulkan);
3. Continue "Apply Changes and Restart"
4. Launcher Opens, select create Writer Document; Writer works as intended.

Expected Results:
By disabling the hardware acceleration, Writer works.
Resetting the User Profile does not fix this issue.
Select "Configure" and CHECK "Disable hardware acceleration (OpenGL, OpenCL,
Vulkan);
3. Continue "Apply Changes and Restart"
4. Launcher Opens, select create Writer Document; Writer works as intended.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.3.7.2 (x64) / LibreOffice Community
Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to