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

            Bug ID: 174150
           Summary: Crash on Startup
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
When starting LibreOffice Writer it crashes and provides an option to "enter
troubleshoot mode". Restore from backup is selected but there is no backup;
this is a fresh install. I performed a Reset on settings, user profile, and
user interface mods: No change in condition. I have already uninstalled(using
REVO UNINSTALLER) and reinstalled from .EXE and .MSI each: no change in
condition. This only happens when I start Writer by itself; I don't need to
load the suite launcher.
I am using LibreOffice 26.8.1 on.....

Device Name     Sylvia
Processor       Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz   3.60 GHz
Installed RAM   32.0 GB
Graphics Card   NVIDIA GeForce GT 640 (2 GB)
Device ID       03158CF8-D84C-4650-9668-6A3AB0B0282A
Product ID      00326-10009-10918-AA363
System Type     64-bit operating system, x64-based processor
Pen and touch   Pen support
Edition Windows 10 Home
Version         22H2
Installed on    ‎12/‎28/‎2024
OS Build        19045.7807


Steps to Reproduce:
1. Run Writer independently (do not launch suite launcher)
2.
3.

Actual Results:
Crash with options to file crash report and enter troubleshoot mode or continue
normally without sending a crash report

Expected Results:
Launch Writer without flipping me an attitude.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 26.8.1.1 (X86_64)
Build ID: bf6ef2662401c7d6dce671ab4deb26ee0af3a7c1
CPU threads: 8; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Raster;
VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

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

Reply via email to