This bug was filed from the crash reporting server and is br-3553fd79-1c93-4e46-9bcd-79ea9fd600ea. ========================================= FILEOPEN Crash happens when opening an odb file or when creating a new database (HSQLDB). I've tried with different vesions of libreoffice (24.2.3, 24.2.1, 7.6.7) with no success while at least the 24.2.1 was able to open it some weeks ago. The file can be opened on another linux system (version 6.4.4.2) and on a mac (version 24.2.3).
Which version of LO do you use? There are differences between the versions of Linux distributions and packages original from LibreOffice. This is a build from LO directly: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded This is a build from my openSUSE distribution. See the short Build ID. Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded You could also try to start LO by SAL_USE_VCLPLUGIN=gen ./soffice So we could see if it only happens with gtk3.
Hello ! Starting with SAL_USE_VCLPLUGIN=gen ./soffice does work ! I can use Libreoffice Base with that env var. I'm used to official libraries from Libreoffice (rpm version), but the problem also appears with Manjaro packages. I've also managed to launch Base using version 6.4.7.2 downloaded from your archives, without the SAL_USE_VCLPLUGIN env var.
Another ineresting info : Base works well using X11 21.1 (no env var) while it crashes when using Wayland 1.22
I've tried the different values for SAL_USE_VCLPLUGIN listed in https://wiki.documentfoundation.org/Development/Environment_variables. All of them make Base crash except gen and qt5. Another magic env var to make Base work : GDK_BACKEND=x11
I don't get a crash after creating a new embedded HSQL database, on Ubuntu 22.04 + GNOME 42.9 + Wayland with: Version: 24.2.4.2 (X86_64) / LibreOffice Community Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Can you share a sample file that consistently crashes?
Dear f.fondement, 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 f.fondement, 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