Created attachment 150560 [details] Open the query and insert a new row as described Open the attached database-file. Open the query, which has been created by the GUI. Query shows the content of 2 table. Write in new row "ID_N"='3', "Name"='Robert', "Sport_ID"='1' and change to next row. "Name" 'Robert' will appear with "Sport" 'football'. Write in new row "ID_N"='4', "Name"='Else', "ID_S"='3', "Sport"='dancing' LO will crash immediately, because the query couldn't handle the insert for two tables. If you try the same and set also "Sport_ID"='3' it doesen't crash buit leads to an error. Expected behaviour: Show an errormessage. LO shouldn't crash. This bug appears with LO 6.2.2.2 an embedded Firebird, but could also reproduced with embedded HSQLDB. Tested with OpenSUSE 15 64bit rpm Linux
I see a SIGABRT in bibisect-linux-64-6.3 repository source hashes c8c0292c (2019-04-04) and a20a2d73 (2018-11-12) running on debian buster. I am setting status NEW. In the newer of those versions, if I close and reopen the query before the second update, upon leaving column Sport LO presents msgbox: LibreOfficeDev Base Error inserting the new record firebird_sdbc error *violation of FOREIGN KEY constraint "INTEG_5" ON TABLE "tblName" *Foreign key reference target does not exist *Problematic key value is ("Sport_ID" = 3) caused by 'isc_dsql_execute' Funnily enough, a local build of of s-h 3abcd615 (2019-02-02), configured CC=ccache /usr/bin/gcc CXX=ccache /usr/bin/g++ CCFLAGS=-Wshadow --with-jdk-home=/usr/lib/jvm/default-java --enable-split-debug --enable-gdb-index --enable-ld=gold --enable-option-checking=fatal #--enable-dbgutil #--enable-debug --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src --without-package-format built and running on debian buster, presents the msgbox even with both updates performed within the same execution of the query.
Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Crash doesn't appear any more in LO 7.1.2.2 on OpenSUSE 15.2 64bit rpm Linux. So I will set this one to WORKSFORME.