Bug 126659 - LibreOffice 6.2.6.1 x86_64 does not start after installing
Summary: LibreOffice 6.2.6.1 x86_64 does not start after installing
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-01 12:13 UTC by Dan Lewis
Modified: 2019-08-06 08:31 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
This file is part of the debugging process. (77.52 KB, text/plain)
2019-08-01 18:57 UTC, Dan Lewis
Details
This is the gdbtrace.log results. (3.60 KB, text/x-log)
2019-08-02 18:27 UTC, Dan Lewis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Lewis 2019-08-01 12:13:51 UTC
Description:
I use Ubuntu 18.04. When attempting to start LO 6.2.6.1, I have tried clicking on the LO icon in the Dock. I have also tried by opening a terminal and entering /opt/libreoffice6.2/program/sbase. In either case, the splash screen appears only for a short period of time and then nothing.

Steps to Reproduce:
1. Download LO 6.2.6.1 from the LO website
2. Extract this file to ~/Downloads/LO/ using Archive Manager
3. Open a terminal.
4. Using cd, browse to the DEBS folder for LO 6.2.6.2.
5. Use dpkg -i *.deb to install 6.2.6.1.
6. Enter /opt/libreoffice6.2/program/sbase and press enter.
7. The splash screen appears for a few seconds while the hour glass cursor shows   
   something is running.
8. The screen disappears and the cursor begins to blink in the terminal. There 
   is no message in the terminal showing what might have happened.

Actual Results:
The program started to run for a short time before dying.

Expected Results:
I expected the program to begin running.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment: I had been running 6.2.5.2 using an icon in the dash to start it. After installing 6.2.6.1, I clicked this icon with the same results: a splash screen for a short time and then nothing.
Comment 1 Michael Stahl (allotropia) 2019-08-01 12:24:12 UTC
please try the following:

/opt/libreoffice6.2/program/sbase --strace
-> file "strace.log" is created, please attach

LD_DEBUG=libs LD_DEBUG_OUTPUT=foo /opt/libreoffice6.2/program/sbase
-> files "foo.*" are created, the one with the largest size is typically the interesting one

SAL_USE_VCLPLUGIN=gen /opt/libreoffice6.2/program/sbase
-> does this start?

(do we have a wiki page where i could add these instructions?)
Comment 2 Dan Lewis 2019-08-01 18:57:23 UTC
Created attachment 153097 [details]
This file is part of the debugging process.

When I ran LD_DEBUG=libs LD_DEBUG_OUTPUT=foo /opt/libreoffice6.2/program/sbase, this was by far the largest file (79KB vs 13KB or smaller).
Comment 3 Dan Lewis 2019-08-01 19:00:28 UTC
I also ran /opt/libreoffice6.2/program/sbase --strace. I can not attach it as it contains 507.9MB. This is much larger than what this web page will accept.
Comment 4 Michael Weghorn 2019-08-01 23:03:49 UTC
(In reply to Michael Stahl (CIB) from comment #1)
> [...]
> (do we have a wiki page where i could add these instructions?)

Maybe [1]? (part of this seems to be covered already) That page also contains some other steps that can possibly help to get more relevant information.

(In reply to Dan Lewis from comment #3)
> I also ran /opt/libreoffice6.2/program/sbase --strace. I can not attach it
> as it contains 507.9MB. This is much larger than what this web page will
> accept.

Often, the size of such files can be significantly reduced e.g. by gzipping them.

[1] https://wiki.documentfoundation.org/QA/BugReport/Debug_Information
Comment 5 Michael Weghorn 2019-08-01 23:09:40 UTC
Also, does this still happen if you try with a fresh user profile, e.g. using this command:

/opt/libreoffice6.2/program/soffice -env:UserInstallation=file:///tmp/test
Comment 6 Michael Stahl (allotropia) 2019-08-02 09:18:47 UTC
the attachment doesn't contain any hint as to a library that failed to load, it ends abruptly after loading libvclplug_gtk3lo.so and libgcc3_uno.so so i guess it crashed then.

try "/opt/libreoffice6.2/program/sbase --backtrace", attach the "gdbtrace.log"
Comment 7 Buovjaga 2019-08-02 15:03:00 UTC
(In reply to Michael Stahl (CIB) from comment #1)
> SAL_USE_VCLPLUGIN=gen /opt/libreoffice6.2/program/sbase
> -> does this start?

Dan: did you try this?
Comment 8 Dan Lewis 2019-08-02 18:27:17 UTC
Created attachment 153111 [details]
This is the gdbtrace.log results.

Perhaps the small size of this log file will reveal what is going on fairly quickly.
Comment 9 Dan Lewis 2019-08-02 18:44:12 UTC
(In reply to Buovjaga from comment #7)
> (In reply to Michael Stahl (CIB) from comment #1)
> > SAL_USE_VCLPLUGIN=gen /opt/libreoffice6.2/program/sbase
> > -> does this start?
> 
> Dan: did you try this?

   Yes I did today (UTC -4). It increased the length of time the splash screen was visible for a few additional seconds.
   This is embarrassing: when I renamed the User folder and ran the program, it opened! I have a habit of creating a configure folder for each LO program I use (6.1, 6.2, 6.3). I am also lazy in that I copy the User folder from one of them to another. It has come back to haunt me. I think that this resolves this problem.
Comment 10 Michael Weghorn 2019-08-05 19:25:22 UTC
(In reply to Dan Lewis from comment #9)
>    This is embarrassing: when I renamed the User folder and ran the program,
> it opened! I have a habit of creating a configure folder for each LO program
> I use (6.1, 6.2, 6.3). I am also lazy in that I copy the User folder from
> one of them to another. It has come back to haunt me. I think that this
> resolves this problem.

Thanks for the update! I'm closing this bug as WORKSFORME, since it no longer happens with a fresh user profile. Please just reopen or create a new issue if the problem reappears.
Comment 11 Michael Stahl (allotropia) 2019-08-06 08:31:46 UTC
i disagree with resolving this issue, although to investigate further and possibly fix it we'd probably need the user profile that causes the crash.

Dan, is it possible to attach that?