Bug 126782 - Crash on initial launch centos release 7-6.1810.2.el7.centos.x86_64
Summary: Crash on initial launch centos release 7-6.1810.2.el7.centos.x86_64
Status: RESOLVED DUPLICATE of bug 126351
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.2.5.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-08 17:59 UTC by James Fuqua
Modified: 2019-08-09 11:48 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["Invalid signature"]


Attachments
Crash Dumpfile (134.80 KB, application/vnd.tcpdump.pcap)
2019-08-08 18:00 UTC, James Fuqua
Details
Additional dump files (369.79 KB, application/gzip)
2019-08-08 18:06 UTC, James Fuqua
Details

Note You need to log in before you can comment on or make changes to this bug.
Description James Fuqua 2019-08-08 17:59:15 UTC
Description:
After installing LibreOffice via RPM/Yum LibreOffice_6.2.5.2_Linux_x86-64_rpm
None of the apps will launch unless I use the following command line
SAL_USE_VCLPLUGIN=gen /opt/libreoffice6.2/program/soffice
It produces a DumpFile each time

Steps to Reproduce:
1. Install LibreOffice 6.2.5.2 via Yum
2. Try to launch any app via shortcut or command line


Actual Results:
No apps open, or processes running.

Expected Results:
Program will run with a process.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Comment 1 James Fuqua 2019-08-08 18:00:55 UTC
Created attachment 153242 [details]
Crash Dumpfile
Comment 2 James Fuqua 2019-08-08 18:06:47 UTC
Created attachment 153243 [details]
Additional dump files
Comment 3 James Fuqua 2019-08-08 18:16:03 UTC
This bug appears fixed in the LibreOffice 6.3 release just installed it and it's working correctly.
Comment 4 Xisco Faulí 2019-08-09 09:23:36 UTC
(In reply to James Fuqua from comment #3)
> This bug appears fixed in the LibreOffice 6.3 release just installed it and
> it's working correctly.

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.
Comment 5 Xisco Faulí 2019-08-09 11:48:50 UTC
It seems like a dupe of bug 126351

*** This bug has been marked as a duplicate of bug 126351 ***