Bug 124489

Summary: Cannot install LibreOffice 6.1.5.2 or 6.2
Product: LibreOffice Reporter: Bryan McKenzie <jimkenzie1>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED NOTABUG    
Severity: normal CC: xiscofauli
Priority: medium    
Version: 6.2.2.2 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Bryan McKenzie 2019-04-02 00:15:34 UTC 
Description:
I download the installation file and run it. It says it installs correctly. But when I try to run it, it starts to load, but then crashes with a long-winded message to the effect: " LibreOffice 6.1 Fatal Error The application cannot be started. [content "user"] caught unexpected com.sun.star.deployment.DeploymentException: Extension Manager: failed to read data entry in configuration backend db:file://C:/Users etc. etc etc. " At the end it continues: " PackageRegistryBackend/backenddb.sml"  Obviously this message is of no use whatsoever! I have deleted all previous versions of LibreOffice, did a cold restart - same result I first got this with LO 6.2. Thought it might be the 'technology' fans version problem, so I re-tried with LO 6.1 No difference. Applications not of much use if you can't load the program! It has worked fine for the past several years. Is this a 6.0 version issue? And why does it fail on my laptop computer and not on my desktop? Any clues? I may have to go back to OpenOffice. Please Help! Thank you. JB

Steps to Reproduce:
1.Download installation file
2.Install
3.Won't run!!

Actual Results:
as above under description

Expected Results:
I expect the program to run!


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Bryan McKenzie 2019-04-02 00:27:20 UTC 
UPDATE: Minutes after filling in the bug report I spotted the comment about trying to launch LibreOffice from the command line. It worked! And now it works from the main screen too, which it did not do before. Have no idea what is happening but it seems to have fixed itself. Suggestion: maybe put the idea of launching it from the command line a bit further up in the solution so people wouldn't have to spend so much time filling in the report! Thanks. Cheers, JB
Comment 2 Xisco Faulí 2019-05-06 16:41:03 UTC 
Happy to hear it's working now.
Closing as RESOLVED NOTABUG