This appears when working with a form. While scrolling through the form (not inside a table , just if scrolling the whole form) the application crashes The datasource is an external postgres database, connector is the sdbc driver of libre office. (libreoffice-sdbc-postgresql) The form has a mainform and 4 subforms beneath the mainform. I could detect the same crash with feodora 33 (libre office 7.0.5.2) and Debian Buster (libreoffice 7.0.4.2 from buster-backports) No crash was detected with windows 10 and libreoffice 7.0.5.2 feodora made a bugreport. Please look here for detals, backtrace etc.: https://retrace.fedoraproject.org/faf/reports/123099/ Maybe this bug is related to: Bug 124773 Cheers Alex
I'm quite sure, it's independent from database type and if you copy the structure of your file in another odb file which uses HSQLDB embedded, you should reproduce this. A workaround for Linux would be to not use gtk. If you launch a terminal/console and type: export SAL_USE_VCLPLUGIN=gen you shouldn't reproduce the pb. The pb is gtk implementation in LO calls accessibility part which is quite buggy. Of course, you may try more recent LO version since 7.0, like 7.1 are EOL.
Please: 1. Test with new LO profile folder, just by renaming your existing one 2. Paste Help-About info 3. Test with "SAL_USE_VCLPLUGIN=gen soffice" 4. Test with LO daily master, easy with Appimage creating per https://wiki.documentfoundation.org/Installing_in_parallel/Linux 5. Attach a sample ODB that crasjes, without personal data.
Hi all thanks for your help. After a while it seems the bug is no more existent. I use Libreoffice 7.0.4.2 in Debian bullseye and no crashes :-). Maybe it was a bug in gtk
no sorry, still have the problem, sorry for confusing you. Debian has an outdated version of libreoffice, so it is.
I did try out the suggestion of Julien: export SAL_USE_VCLPLUGIN=gen and it works now. Sorry for the delay and thanks for your help!
(In reply to userxyz from comment #5) > I did try out the suggestion of Julien: > export SAL_USE_VCLPLUGIN=gen > and it works now. > Sorry for the delay and thanks for your help! Great but it's just a workaround since it still crashes with gtk rendering, let's reopen this one then.
Can you provide an ODB that crashes? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the ODB.
Dear userxyz, 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 userxyz, 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