Bug 124668 - Cannot open Libre Office
Summary: Cannot open Libre Office
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.2.2.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-11 00:22 UTC by Lynn Musgrave
Modified: 2019-11-20 03:52 UTC (History)
2 users (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 Lynn Musgrave 2019-04-11 00:22:25 UTC
Description:
I have just completely re-installed my PCLinuxOS system with the latest version (03/19) and fully updated it. I now find that with the addition of Libre Office 6.2.2, I cannot open any part of this office program I have always used, and as a relative novice in linux I do not know why. All I know is that it used to work fine, even with this version of PCLinuxOS which was first installed 5 days after its release. If I try to open office, I get the start up screen very briefly, then it disappears, but the panel on the task bar circles for a bit longer then disappears.It doesn't matter which part of office I am trying to get into either - ALL parts react the same.

Actual Results:
try to open Libre Office and all it does is close down

Expected Results:
nothing


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Xisco Faulí 2019-04-11 09:05:49 UTC
Does it work if you launch it from command line with --safe-mode ?
Comment 2 Lynn Musgrave 2019-04-11 09:32:48 UTC
OK, I have tried it via the Konsole with the same results - tries to open then after a moment closes again. Seems to be doing this no matter how I approach it.
Comment 3 Xisco Faulí 2019-04-16 07:37:48 UTC
What happens if you launch LibreOffice from Konsole with SAL_USE_VCLPLUGIN=gen soffice ?
Comment 4 Lynn Musgrave 2019-04-16 08:03:28 UTC
[lynn@localhost ~]$ SAL_USE_VCLPLUGIN=gen soffice
bash: soffice: command not found
[lynn@localhost ~]$ LibreOffice
bash: LibreOffice: command not found
[lynn@localhost ~]$ LibreOffice SAL_USE_VCLPLUGIN=gen soffice
bash: LibreOffice: command not found
[lynn@localhost ~]$
Comment 5 Jean-Baptiste Faure 2019-04-21 20:27:02 UTC
Please try
SAL_USE_VCLPLUGIN=gen libreoffice

Best regards. JBF
Comment 6 Lynn Musgrave 2019-04-21 20:40:46 UTC
Your comment to use SAL_USE etc is something I do not understand. I did say in my first message that I am a relative novice with Linux systems so this comment means nothing to me. How do I use it and where? In any case, I have again re-installed my system, this time with both KDE and LXDE desktops available and Libre Office now seems working - I do not know what is different with this installation unless it a change made by upgrading from LO 6.2.2 to LO 6.2.3.
Thanks for your efforts anyway
Comment 7 Timur 2019-04-22 08:23:35 UTC
I'm not familiar with PCLinuxOS but this looks like an issue in that OS not in LO.
Please understand Bugzilla is not a support forum. 
Try to find solution in PCLinuxOS forum or reinstall and set back Unconfirmed only if you find out this is LO error.
Comment 8 QA Administrators 2019-10-20 02:34:02 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2019-11-20 03:52:16 UTC
Dear Lynn Musgrave,

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