Created attachment 116005 [details] Activate macros. open the database, open the form and press the button ... 1. Activate LO to execute macros. 2. Open the attached database. 3. Open the form. 4. Press the button «Set all fields except primary key "ID" NULL». The value in the field "firstname" disappears. All other values seem still be saved in the table. 5. Go to next row. 6. Go back to first row. All fields except "ID" are empty. The macro: SUB SetNull(oEvent AS OBJECT) oForm = oEvent.Source.Model.Parent oForm.getByName("firstname").BoundField.UpdateNULL() oForm.getByName("lastname").BoundField.UpdateNULL() oForm.getByName("street").BoundField.UpdateNULL() oForm.getByName("town").BoundField.UpdateNULL() oForm.getByName("birthday").BoundField.UpdateNULL() oForm.getByName("gender").BoundField.UpdateNULL() oForm.UpdateRow END SUB All fields are set NULL except "ID". This works right. UpdateRow works right except refreshing the content of all fields to the new content. Expected behavior: UpdateRow should refresh content of all fields of a row to see the saved values in the table of the database. I set the severity of this bug to «major». For normal users there seem to be data loss while switching from one row to another. Bug appears on OpenSUSE 13.2 64bit rpm Linux with every installed LO-Version including LO 3.*. So I set the version to «Inherited from OOo»
Confirming on Version: 5.1.0.0.alpha1+ Build ID: 8cbb94a2b79dcaf9675125da800b64a85bae52dc Locale : fr-FR (fr.UTF-8) OSX 10.10.3 It is even worse if you proceed from one record to next, clicking on button as you go. By the time you reached record 3, and clicked button, then step back one record, you see the remnants of record 3 in record 2 and even in record 1, where the screen doesn't get updated.
Physically calling Form reload via the context menu in the form doesn't change the result of corrupted screen data display.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Still present in Version: 6.0.0.0.alpha0+ Build ID: 595371e520ce4f64ad9d99a7866bdb8404271b6e CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group
** Please read this message in its entirety before responding ** 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 http://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
Bug still exists in LO 6.1.0.3, OpenSUSE 15, 64bit rpm Linux
On pc Debian x86-64 with master sources updated 2 days ago, I've got a different behaviour. When I click "Set all fields except primary key "ID" NULL", only firstname is cleared. But if I go to next record then go back to previous record, all the fields (except ID) are indeed clear.
First line of the below bt shows where the updated is done with a preparedStatement containing "?" but cache mechanism isn't clear for me. #0 0x00007fffdb04d817 in dbaccess::OKeySet::updateRow(rtl::Reference<connectivity::ORowVector<connectivity::ORowSetValue> > const&, rtl::Reference<connectivity::ORowVector<connectivity::ORowSetValue> > const&, com::sun::star::uno::Reference<com::sun::star::sdbcx::XColumnsSupplier> const&) (this=0x55555c69aa40, _rInsertRow=rtl::Reference to 0x55555c8666e0, _rOriginalRow=rtl::Reference to 0x55555c69cb50, _xTable=uno::Reference to (dbaccess::ODBTableDecorator *) 0x55555c07cc40) at /home/julien/lo/libreoffice/dbaccess/source/core/api/KeySet.cxx:445 #1 0x00007fffdb0eab26 in dbaccess::ORowSetCache::updateRow(__gnu_debug::_Safe_iterator<__gnu_cxx::__normal_iterator<rtl::Reference<connectivity::ORowVector<connectivity::ORowSetValue> >*, std::__cxx1998::vector<rtl::Reference<connectivity::ORowVector<connectivity::ORowSetValue> >, std::allocator<rtl::Reference<connectivity::ORowVector<connectivity::ORowSetValue> > > > >, std::__debug::vector<rtl::Reference<connectivity::ORowVector<connectivity::ORowSetValue> >, std::allocator<rtl::Reference<connectivity::ORowVector<connectivity::ORowSetValue> > > > > const&, std::__debug::vector<com::sun::star::uno::Any, std::allocator<com::sun::star::uno::Any> >&) (this=0x55555c699fa0, _rUpdateRow=rtl::Reference to 0x55555c8666e0, o_aBookmarks=std::__debug::vector of length 0, capacity 0) at /home/julien/lo/libreoffice/dbaccess/source/core/api/RowSetCache.cxx:1338 #2 0x00007fffdb0acf9a in dbaccess::ORowSet::updateRow() (this=0x55555b6922e0) at /home/julien/lo/libreoffice/dbaccess/source/core/api/RowSet.cxx:954 #3 0x00007fffacf37b85 in frm::ODatabaseForm::updateRow() (this=0x55555b691b70) at /home/julien/lo/libreoffice/forms/source/component/DatabaseForm.cxx:3434
Dear robert, 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 http://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
Bug still exists in LO 6.3.1.2, OpenSUSE 15 64bit rpm Linux.
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
Bug is still the same with LO 7.2.0.4 on OpenSUSE 15.2 64bit rpm Linux.
(In reply to Robert Großkopf from comment #10) > Bug still exists in LO 6.3.1.2, OpenSUSE 15 64bit rpm Linux. > https://indianporn.love it's bad and sad :(
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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug is still the same with LO 24.2.4.2 on OpenSUSE 15.6 64bit rpm Linux.