Bug 147389 - After installing LO 7.3.0.3 LO doesn't start
Summary: After installing LO 7.3.0.3 LO doesn't start
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-12 10:42 UTC by BRANDT
Modified: 2022-08-17 18:21 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 BRANDT 2022-02-12 10:42:19 UTC
Description:
I have just installed LO 7.3.0.3 on Windows 10 Pro, I restarted the PC and now LO doesn't start. In TaskManager 2 process start and stop in less than 2 seconds with no message.

Steps to Reproduce:
1.Install LO 7.3.0.3
2.Restart computer
3.start LO (writer)

Actual Results:
LO doesn't start with no message.

Expected Results:
it starts


Reproducible: Always


User Profile Reset: No



Additional Info:
no message, LO doesn't start
Comment 1 BRANDT 2022-02-12 10:59:23 UTC
With CMD.EXE it gives no message start and stop in less than 2 seconds :

C:\>"C:\Program Files\LibreOffice\program\soffice.exe"
C:\>

It's the same starting with the icone on the desktop 
or with Windows program list Libreoffice then LO Writer

After installing LO 7.3.0.3 i also installed HelPack French
Comment 2 BRANDT 2022-02-12 11:40:39 UTC
I uninstalled 7.3.0.3 and installed 7.2.5.2
After restarting the PC i started Writer which trys to recover an unsaved document.
This morning i opnened writer(7.2.4) and then i got a message saying 7.2.5 is available. So i downloaded 7.3.0.3 and installed it. During installation it ask to close previous writer so i quit writer 7.2.4 without saving the document (it was nothing in).
So when 7.3.0.3 started it had this document to recover...
Comment 3 Buovjaga 2022-02-12 12:03:18 UTC
Can you launch it in Safe mode, from the Windows start menu entry?
Comment 4 BRANDT 2022-02-12 15:48:38 UTC
I have uninstalled it. I need one so i installed 7.2.5. I will reinstall it soon.
Comment 5 Buovjaga 2022-02-12 21:34:04 UTC
By the way, you can install an unstable version that will not mess with your stable version. Win-x86_64@tb77-TDF from https://dev-builds.libreoffice.org/daily/master/current.html

You don't need to uninstall your stable one to try that build. It installs separately. Might be interesting to try it.
Comment 6 BRANDT 2022-02-13 13:07:55 UTC
Hourra,

With that version it works fine.
Thank you very very much.
The design looks more cheerful and pleasant
Very nice job.

Is it also an helppack in french ?
Tanks again,
rené.
Comment 7 Buovjaga 2022-02-13 13:27:53 UTC
Interesting to hear. The French help pack for the latest build is https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/2022-02-13_04.16.45/LibreOfficeDev_7.4.0.0.alpha0_Win_x64_helppack_fr.msi

However, I don't recommend using an unstable build for important work. It would be best to continue using 7.2.5 until a new minor release of 7.3 will be released in a few weeks: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.1_release

Hopefully 7.3.1 would work better for you.

There are also daily builds for the unreleased, upcoming 7.3.x https://dev-builds.libreoffice.org/daily/libreoffice-7-3/Win-x86_64@tb77-TDF/
Comment 8 Timur 2022-02-13 16:43:31 UTC
We don't know if big was resolved in unstable master 7.4+ or all was needed was new profile. 
So, one that next 7.3 is out, please install. If there's a problem, try to reset or remove LO profile, as indicated in bug report form. 
Until than, this bug has no action, so let's keep it in Needinfo status, so there will be a reminder later.
Comment 9 QA Administrators 2022-08-13 03:41:08 UTC Comment hidden (obsolete)
Comment 10 BRANDT 2022-08-17 16:04:46 UTC
as documented in comment 6 the version dev 7.4.0.0 solved the problem.


Since that time i left windows for linux, so i am unable to do more tests.
Sorry, for me you can close this bug report

Man<y thanks,

Rene