Bug 151024 - New version fails to start
Summary: New version fails to start
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-17 10:03 UTC by Ian
Modified: 2023-04-17 03:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian 2022-09-17 10:03:07 UTC
Description:
Just downloaded ver 7.4.1
Fails to start

Steps to Reproduce:
1.Start
2.
3.

Actual Results:
Briefly registers in process list, but then closes without displaying any screen output

Expected Results:
Presumably it should start


Reproducible: Always


User Profile Reset: No



Additional Info:
Using Windows 10 on MSI GS76 Stealth
Comment 1 Buovjaga 2022-09-17 11:20:35 UTC
Did version 7.4.0 start for you?
Can you start it from the "LibreOffice Safe mode" Windows start menu entry?
Comment 2 Timur 2022-09-17 15:42:25 UTC
After you try Safe Mode, please do User Profile Reset,  i. e. rename or delete LO user profile folder. 

If that doesn't help, next step is to start LO without Skia.
Comment 3 QA Administrators 2023-03-17 03:26:54 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2023-04-17 03:20:19 UTC
Dear Ian,

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