Bug 148994 - Libre office writer crash on start in Windows 10
Summary: Libre office writer crash on start in Windows 10
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.3.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-09 09:30 UTC by minimaal6tekens@gmail.com
Modified: 2023-02-01 03:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Crash report (26.26 KB, application/octet-stream)
2022-05-09 09:32 UTC, minimaal6tekens@gmail.com
Details

Note You need to log in before you can comment on or make changes to this bug.
Description minimaal6tekens@gmail.com 2022-05-09 09:30:50 UTC
Description:
When I start Writer, it crashes (after a few seconds). 

The first time I opened calc (I opened a .odt document), it crashed as wel. After opeing a blank spreadsheet, this was fixed. But not for writer.

I tried the following:
- https://ask.libreoffice.org/t/libreoffice-7-keeps-crashing/55447
reboot safe-mode => not fixed
- https://ask.libreoffice.org/t/solved-libreoffice-crashes-immediately-after-startup-or-opening-a-document/74612
turn off / on => not fixed (and in writer: cannot execute, because by the time I am in this menu, writer will be crashed). 
- https://ask.libreoffice.org/t/crashing-on-startup-every-time/44676
add soffice.bin to acces folder => not fixed



 


Steps to Reproduce:
1.Start libre office writer
2.
3.

Actual Results:
crash (and disappear window)

Expected Results:
Not a crash (the window wil stay and I can do word-processing)


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Computer:
- AMD Reyzen 1600, 16gb, SSD, Radion 6600 
- OS: Windows 10 (19044.1645)
Comment 1 minimaal6tekens@gmail.com 2022-05-09 09:32:23 UTC
Created attachment 180009 [details]
Crash report
Comment 2 minimaal6tekens@gmail.com 2022-05-09 09:37:08 UTC
It is LO 7.3.3.2 (x64). Could not select version in list above.
Comment 3 Dieter 2022-05-22 04:56:04 UTC
(In reply to minimaal6tekens@gmail.com from comment #1)
> Created attachment 180009 [details]
> Crash report

Can't open that file. Please add link to crash report.
Comment 4 Timur 2022-07-04 19:07:13 UTC
Please clarify if you tried both to start in save mode via Help menu and to rename LO user folder. 
Also paste Help-About and try to change ie turn off Skia, if in Tools-Options-View.
If crash continues, and it's important if just with Skia or anyway, please use https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg to provide a backtrace for the crash.
Comment 5 Timur 2022-07-04 19:19:33 UTC
Also please write of you have anti-virus and try to run without it. 
And try to install Lo 7.3.4 preferably without anti-virus.
Comment 6 QA Administrators 2023-01-01 03:24:15 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2023-02-01 03:20:44 UTC
Dear minimaal6tekens@gmail.com,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp