Bug 123162 - Libreoffice Crashes on Linux and Windows
Summary: Libreoffice Crashes on Linux and Windows
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.2.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-04 16:55 UTC by Irfan Ali Dogar
Modified: 2019-09-04 04:29 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 Irfan Ali Dogar 2019-02-04 16:55:25 UTC
Description:
We have been using Libreoffice 6.2.x as service on Linux/Windows using our Java application. While converting the document sometimes LibreOffice service crashes without any reason, this is not a consistent behavior but is happening quite frequently. On linux we found following crash information:

[New Thread 0x7fffd5f27700 (LWP 8036)]
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libreoffice/program/libswlo.so-gdb.py", line 12, in <module>
    import importlib
ImportError: No module named importlib
Detaching after fork from child process 8037.


We tried everything possible, then finally decided to downgrade LibreOffice and with LibreOffice 4.3.7.2 430(Build:2) this issue doesn't happen.

Can this please be looked at urgently? 

Actual Results:
Setup LibreOffice as service on Linux/Windows and convert multiple docx documents.

Expected Results:
LibreOffice Application shouldn't crash


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Julien Nabet 2019-02-04 20:04:12 UTC
Without more information, I don't think dev experts may help.

It may be interesting to find one specific document which crashes it.
Then, try to open and convert it manually by opening on LO and save in a different format.

If you can reproduce this, either you can attach the document (have in mind to remove any confidential/private part from it) or you can try to retrieve a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information)
Comment 2 QA Administrators 2019-08-04 05:50:09 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-09-04 04:29:53 UTC
Dear Irfan Ali Dogar,

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