Bug 144403 - FILEOPEN libreoffice crashes when opening/creating new document
Summary: FILEOPEN libreoffice crashes when opening/creating new document
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.1.3.1 rc
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-09 10:21 UTC by florian.k2000
Modified: 2023-11-08 03:15 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
valgrind report (10.04 KB, text/plain)
2021-09-09 10:22 UTC, florian.k2000
Details
strace of Version 7.1.6.2 (6.57 KB, text/x-log)
2021-10-02 08:40 UTC, florian.k2000
Details
Backtrace of version 7.2.5 (12.89 KB, text/x-log)
2022-02-16 11:04 UTC, florian.k2000
Details
Backtrace of version 7.3.0 (12.28 KB, text/x-log)
2022-02-16 11:05 UTC, florian.k2000
Details

Note You need to log in before you can comment on or make changes to this bug.
Description florian.k2000 2021-09-09 10:21:12 UTC
Description:
Libreoffice crashes after opening a document, no matter which component is opened.
I guess its a rendering issue.
The stack-trace points to an qt function . (trace is attatched)
Using "SAL_USE_VCLPLUGIN=gen libreoffice" to start libreoffice works with no problem.
Reinstallation of libreoffice and qt did not help.

Steps to Reproduce:
1. /usr/lib/libreoffice/program/soffice.bin --norestore --writer

Actual Results:
crashes instantly, restore mode flashes up, crashes again

Expected Results:
start normally, open new document


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.9.16-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz
Memory: 7.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

libreoffice: 
Version: 7.1.5.2 / LibreOffice Community
Build ID: 10(Build:2)
CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: kf5
Locale: de-DE (de_DE.UTF-8); UI: de-DE
7.1.5-2
Calc: threaded
Comment 1 florian.k2000 2021-09-09 10:22:08 UTC
Created attachment 174922 [details]
valgrind report
Comment 2 Xisco Faulí 2021-09-29 15:42:15 UTC
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Comment 3 florian.k2000 2021-10-02 08:38:30 UTC
I had reset the profile, which did not help either.
This problem also exists in version 7.1.6.2.0+, although the strace looks a bit different here.
Comment 4 florian.k2000 2021-10-02 08:40:33 UTC
Created attachment 175454 [details]
strace of Version 7.1.6.2
Comment 5 Xisco Faulí 2021-10-04 09:27:08 UTC
Does it work if you launch LibreOffice from commandline with 'SAL_USE_VCLPLUGIN=gen' ?
Comment 6 florian.k2000 2021-10-04 09:38:13 UTC
Yes, it does for both versions
Comment 7 Kevin Suo 2022-01-21 01:41:36 UTC
Does it crash with the newer 7.2 or 7.3, or even master versions?
Comment 8 florian.k2000 2022-02-16 11:03:28 UTC
Both versions LibreOffice 7.2.5.2.0 20(Build:2) and LibreOffice 7.3.0.3 30(Build:3) don't work out of the box and terminate in a coredump (backtraces attached).
Using SAL_USE_VCLPLUGIN=gen or SAL_USE_VCLPLUGIN=gtk3 does work without any problems though.
Comment 9 florian.k2000 2022-02-16 11:04:39 UTC
Created attachment 178302 [details]
Backtrace of version 7.2.5
Comment 10 florian.k2000 2022-02-16 11:05:09 UTC
Created attachment 178303 [details]
Backtrace of version 7.3.0
Comment 11 Hossein 2023-04-10 09:56:21 UTC
Looking at the gdb traces, two problems with Java are visible:

1. These warnings:
warning: the debug information found in "/usr/lib/jvm/java-11-openjdk/lib/server/libjvm.debuginfo" does not match "/usr/lib/jvm/java-11-openjdk/lib/server/libjvm.so" (CRC mismatch).
...
(A similar problem is discussed here: https://access.redhat.com/solutions/333463)

2. Segfault at libjvm.so:

Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
0x00007fff6c85362d in ?? ()
#0  0x00007fff6c85362d in  ()
#1  0x0000000000000246 in  ()
#2  0x00007fff6c853724 in  ()
#3  0x00007fff89f956a8 in  () at /usr/lib/jvm/java-11-openjdk/lib/server/libjvm.so
#4  0x00007fffffffa7f0 in  ()
#5  0x00007fff89bf5689 in  () at /usr/lib/jvm/java-11-openjdk/lib/server/libjvm.so

A similar problem with 32 bit Java is discussed here:
https://ask.libreoffice.org/t/libreoffice-base-crashes-on-32bit-linux/27032/5

I think it helps that you test LibreOffice with another 64 bit JRE (or even without a JRE) to see if the problem is caused by a JRE problem/misconfiguration.

You can download JDK (which also includes JRE) from several sources, including:
https://developers.redhat.com/products/openjdk/download
https://learn.microsoft.com/en-us/java/openjdk/download
https://www.oracle.com/java/technologies/downloads/
https://adoptium.net/
Comment 12 QA Administrators 2023-10-08 03:16:18 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2023-11-08 03:15:41 UTC
Dear florian.k2000,

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