Description: I use LibreOffice 7.0.4.2 00(Build:2) from the offifial "extra" repository for archlinuxarm. Everything in LibreOffice works as expected but the Writer. Regardless of whether I - open lowriter from CLI - open "New Textdocument" from GUI startpage - open an existing document associated with lowriter from anywhere I am presented with the information that lowriter has crashed but that I can re-create my last documents (sorry, I use the German language version, it might be another word for "re-create", I'm sure it's clear what happens, though, I hope). When I press - OK / Wiederherstellen, I get a success window, in which I click on OK, which in turn brings back the "has crashed" one, .... ad infinitum - cancel, I immediately get the "has crashed" window back, .... ad infintum Strangely enough, the flatpak build LibreOffice The LibreOffice productivity suite org.libreoffice.LibreOffice 7.0.1.2 stable flathub works like a charm. Steps to Reproduce: 1. start lowriter from cli 2. chose "New Textdocument" from LibreOffice Startpage 3. open any associated document from within LibreOffice or any file manager Actual Results: The Writer component offers the document repair window for new starts after crashes, does not re-create the file but circles through "has crashed" "re-created" "has crashed" info. No window is opened, no document started, no process "lowriter" started in the system. Expected Results: The Writer component should start, a window should be opened and a process should appear in the system. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Build that shows this bug: Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE 7.0.4-1 Calc: threaded Build that works: Version: 7.0.1.2 Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Flatpak Calc: threaded It doesn't matter at all if there's a User Profile present or not.
I've now managed to find a way to get some more info: $ lowriter --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x39f8c)[0xb6efff8c] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3a154)[0xb6f00154] /usr/lib/libc.so.6(__default_rt_sa_restorer+0x0)[0xb6ca6df0] /usr/lib/libc.so.6(gsignal+0xbc)[0xb6ca5aa0] Hope that helps.
Hello, 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 pegu1, 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 pegu1, 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