Created attachment 119709 [details] Open the form - no color except grey for border of a tablecontrol Open the attached database. Open the form. There are three tablecontrols: First should have a black border, second a blue border, third a red border. Last version which will show the color of the border here is LO 4.0.0.1 First version I have installed, which fails, is 4.0.2.2 My System: OpenSUSE 13.2 64bit rpm Linux, KDE/XFCE tested, also with LO 5.0.3.1 and a fresh profile.
On pc Debian x86-64 with master sources updated today, I could reproduce this. Keyid language allowed me to know that RID_STR_BORDERCOLOR was used but searching this on Opengrok doesn't help much.
Seems there has been changed something in the daily build: Colored border could be seen while editing a form on Version: 5.1.0.0.alpha1+ Build ID: b58be9e8f983d1d0ca10a6ebe903c9a6482cefdd TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-11-14_00:35:50 But couldn't be seen while opening the form for input data. With Version: 5.1.0.0.alpha1 it couldn't be seen while editing and also while opening form for input data.
Added keyword "regression". Works right in LO 4.0.0.3, fails with LO 4.0.2.2.
Adding keyword 'bibisectRequest'.
** 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-20170929
Bug appears also in LO 5.4.2.1 on OpenSUSE 42.2 64bit rpm Linux.
Unfortunately, with some builds in the 43all Linux bibisect repo, the form cannot be opened. There are only 'skip'ped commits left to test. The first bad commit could be any of: 0a0d80b18dc905ee56faaad81c2d6839f8e0172d 1273b9e25faacf414c611503c2a11283af274044 2cb4591ac9908e86e6e0844714ce74f2c5f0d813 c6a69c23e32b372e1f279f1a5ea6aa0a6cf52968 a71a4447320f177181c9cff9f7c6fd93802cbd8e ef67f79d5c082070b3185286da0bacd714bb61b4 21974bfa867971881326fe3694bc1fb365f20ae1 We cannot bisect more!
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 on LO 6.2.5.2, OpenSUSE 64bit rpm Linux. Note: Could also be it couldn't be tested any more, because borders weren't shown around the control any more, see bug 122661
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 appears also in LO 7.1.4.2 on OpenSUSE 15.2 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists with LO 7.5.5.1 on OpenSUSE 15.4 64bit rpm Linux.
(In reply to Buovjaga from comment #7) > Unfortunately, with some builds in the 43all Linux bibisect repo, the form > cannot be opened. > > There are only 'skip'ped commits left to test. > The first bad commit could be any of: > 0a0d80b18dc905ee56faaad81c2d6839f8e0172d > 1273b9e25faacf414c611503c2a11283af274044 > 2cb4591ac9908e86e6e0844714ce74f2c5f0d813 > c6a69c23e32b372e1f279f1a5ea6aa0a6cf52968 > a71a4447320f177181c9cff9f7c6fd93802cbd8e > ef67f79d5c082070b3185286da0bacd714bb61b4 > 21974bfa867971881326fe3694bc1fb365f20ae1 > We cannot bisect more! Clicking on the links, I got only 404.
(In reply to Julien Nabet from comment #14) > (In reply to Buovjaga from comment #7) > > Unfortunately, with some builds in the 43all Linux bibisect repo, the form > > cannot be opened. > > > > There are only 'skip'ped commits left to test. > > The first bad commit could be any of: > > 0a0d80b18dc905ee56faaad81c2d6839f8e0172d > > 1273b9e25faacf414c611503c2a11283af274044 > > 2cb4591ac9908e86e6e0844714ce74f2c5f0d813 > > c6a69c23e32b372e1f279f1a5ea6aa0a6cf52968 > > a71a4447320f177181c9cff9f7c6fd93802cbd8e > > ef67f79d5c082070b3185286da0bacd714bb61b4 > > 21974bfa867971881326fe3694bc1fb365f20ae1 > > We cannot bisect more! > > Clicking on the links, I got only 404. Bugzilla linkifies hashes these days, but those hashes are for binaries in the 43all repo. Source hashes: 4ba8147f61fadb4e8ae7abc0ad5c9e928edf4baa cf04745f7a027594fd64a493c276a8280dbccfe1 8201c8a5f680947c2e855504be321afb1e5bc06a cac1f33e839469d884730350e46a21d92fb442f2 9afb6e1e38c362a768e8e981f7b03cf8bcaf22cf 099198a4224778fe6e43f5dc13b5b9b1b4dc828c 9e8957de203bb9abb208516ad32aee9527feb67b
(In reply to Buovjaga from comment #15) > ... > Bugzilla linkifies hashes these days, but those hashes are for binaries in > the 43all repo. > > Source hashes: > 4ba8147f61fadb4e8ae7abc0ad5c9e928edf4baa > cf04745f7a027594fd64a493c276a8280dbccfe1 > 8201c8a5f680947c2e855504be321afb1e5bc06a > cac1f33e839469d884730350e46a21d92fb442f2 > 9afb6e1e38c362a768e8e981f7b03cf8bcaf22cf > 099198a4224778fe6e43f5dc13b5b9b1b4dc828c > 9e8957de203bb9abb208516ad32aee9527feb67b Far better, thank you! :-)