Description: After firing up LibreOffice and waiting for a short while, LO suddenly dies. You don't need to do anything. Just wait. Steps to Reproduce: 1.Start LO 2.Wait 3.Crash Actual Results: LO restarts and ask for recovering a document, if any. Expected Results: LO restarts as usual. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Here are some information on my hardware. Version=7.1.0.0 BuildID=e0c1fdcab23dbd2b7a0a7227557d7afc41b49bd7 URL=https://crashreport.libreoffice.org/submit/ UseSkia=false AdapterVendorId=NVIDIA Corporation AdapterDeviceId=GeForce GTX 1060 3GB/PCIe/SSE2 UseOpenGL=true Language=en-US ShutDown=true Linux 5.8.13-200.fc32.x86_64 #1 SMP Thu Oct 1 21:49:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux My system Fedora 32, with the latest and greatest patches and the processor is a Intel Xeon E3-1230. Have tested with OpenGL removed. It's the same result, dies after a while.
Does it work if you launch LibreOffice in safe mode? I do believe the crash might be related to skia
(In reply to Xisco Faulí from comment #1) > Does it work if you launch LibreOffice in safe mode? I do believe the crash > might be related to skia Linux edition doesn't use Skia? Or has this been changed in Master? Could also be profile corruption. Backend issue GEN/GTK3/KDE5 Some not matching binary? And are talking about one of the Snap/flat/Appimage or a installed version?
Safe mode does not prevent LO from crash, it dies. As I can see in /home/leng/.config/libreofficedev/4/crash/dump.ini, Fedora 32 does not use skia. ProductName=LibreOffice Version=7.1.0.0 BuildID=e0c1fdcab23dbd2b7a0a7227557d7afc41b49bd7 URL=https://crashreport.libreoffice.org/submit/ UseSkia=false AdapterVendorId=NVIDIA Corporation AdapterDeviceId=GeForce GTX 1060 3GB/PCIe/SSE2 UseOpenGL=true Language=en-US ShutDown=true I have cleared the user profile many times and it does not help. My GUI is XFCE DeskTop. For now I am looking forward to Fedora 33 and will test the MATE-COMPIZ DeskTop. I got it from the following ULR: https://dev-builds.libreoffice.org/daily/master/current.html Linux-rpm_deb-x86_64@86-TDF (rpm) so it's an installed version. I have not tested the latest version, this version is one day after. Hope that this will help you.
(In reply to Telesto from comment #2) > ... > Linux edition doesn't use Skia? Or has this been changed in Master? > ... It's possible to use SKIA on Linux with these: SAL_USE_VCLPLUGIN=gen SAL_ENABLESKIA=1 In my case, it'll use Skia/Vulkan. You can also choose SAL_FORCESKIA=1 and SAL_SKIA with "raster" or "vulkan" value. See vcl/README.vars
I can't reproduce this since I use AMD/Radeon card. Perhaps this https://cgit.freedesktop.org/libreoffice/core/commit/?id=614d310751d1a32baec85c11637fb3813a9dd749 may help author Luboš Luňák <l.lunak@collabora.com> 2020-09-28 15:13:08 +0200 committer Luboš Luňák <l.lunak@collabora.com> 2020-09-29 09:58:16 +0200 commit 614d310751d1a32baec85c11637fb3813a9dd749 (patch) tree b81ee0366291b7fe0412cf9b841abd7030685ecb parent f8d6eb6f171dbcf7e3aa4afa0da32bd504f473dc (diff) disable VSync for Skia/Vulkan on Linux/nVidia It causes freezes. This can be changed later to a blacklist of older drivers once fixed drivers are actually available.
This can be anything. Please provide a backtrace of the crash (https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace).
Created attachment 166363 [details] Backtrace log-file LO7-dev debug Downloaded Linux-rpm_deb-x86_64@86-TDF-dbg, 20-10-14, 5d9e330, and run a backtrace. Hope this will help you.
There's no actual backtrace in the output, you need to type the 'bt' command (item 5. in the howto).
Created attachment 166378 [details] Back trace generated with out debug information. LO dies about 30 -40 seconds after it has been launched. You don't need to do anything.
Hello! I think the problem is connected with XFCE Desktop. During the afternoon I installed Fedora 33 (beta) and updated it. Now I'm run the Mate-Desktop and and LO 7.0.2.2 and nothing weird happens. It looks stable as far as I can see. I hope this will help you to further.
[Automated Action] NeedInfo-To-Unconfirmed
Hello Lars-Erik, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Lars-Erik, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Lars-Erik, 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