Problem description: If you compare a text document with another which is password protected, you are asked for the password but the comparison does not occur Steps to reproduce: 1. open an existing text document, eg a.odt 2. make some minor change and save this document as a new file with password, eg. a_mod.odt 3. close a_mod.odt and open a.odt 4. menu Edit > Compare document 5. choose a_mod.odt 6. LibreOffice ask for the password. Type in the password. Current behavior: nothing happens Expected behavior: "Accept or Reject Changes" is shown with the minor change done at step 2. Remark: at this moment if you try to open a_mod.odt it opens in read-only mode, which proves that the file is already opened even it is not visible.
Confirmed under MS-Windows-XP and Linux Ubuntu 10.04 x86_64. Side note: Bug report assistant: nice job :-) Best regards. JBF
"Current behavior: nothing happens" No, we are just getting an error message specifying that the entered password is incorrect whereas it's the good password. Error loading document file:///FILE_PATH/FILE_NAME.ods Read-Error. The wrong password has been entered.
(In reply to comment #2) > "Current behavior: nothing happens" > > No, we are just getting an error message specifying that the entered password > is incorrect whereas it's the good password. > > Error loading document file:///FILE_PATH/FILE_NAME.ods > Read-Error. > The wrong password has been entered. Sorry. It was for #41544. Already added.
Still present in LibO 3.5.2b2+
I tried with Encryption password and 3.4.1RC1 (WIN7 64bit) and got reporter's result, same with [Reproducible] with "LibreOffice Portable 3.3.0 - WIN7 Home Premium (64bit) German UI [OOO330m19 (Build:6) tag libreoffice-3.3.0.4]", LibO Master 3.6, OOo 3.3, so this is inherited from OOo @william@gathoye.be <http://wiki.documentfoundation.org/BugReport_Details#Version> @Jean-Baptiste Faure: Do you agree with my results?
Created attachment 59579 [details] test kit Do your own tests, password is "1"
(In reply to comment #5) > [...] > @Jean-Baptiste Faure: > Do you agree with my results? Yes, I agree. I asked on FR discuss ML for tests on legacy version of OOo and I got the confirmation that the bug is already there. That said there is an obvious workaround: before comparing the files, save a copy without password of the second file. Best regards. JBF
*** Bug 80994 has been marked as a duplicate of this bug. ***
** 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 (4.4.1 or later): 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
Gentoo Linux (current) app-office/libreoffice-bin-4.4.3.2 Current behavior (not changed): nothing happens
** 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.1.5 or 5.2.1 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-20160920
ok, this is getting irritating because there is no progress after 5 YEARS at all. bugs does not disappear by itself and there is no point asking (even using automated bots) to retest if you done nothing. This is the last year when I'm testing it. Gentoo Linux (current) app-office/libreoffice-bin-5.1.4.2 Current behavior (not changed): nothing happens
*** Bug 112374 has been marked as a duplicate of this bug. ***
** 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
Repro 6.2+
I'm not downloading the latest rev, but this now works in the version I am running: Version: 5.4.7.2 (x64) Build ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU threads: 2; OS: Windows 6.19; UI render: default; Locale: en-US (en_US); Calc: group There is still plenty of weirdness in trying to compare files, some of it quite irritating, but this problem (asks for password, uses it to open file, then does nothing) seems to have been fixed. My heartfelt thanks to whoever made it work. -- Dave
Reproduced with Lo 6.3+.
One of the main features of a home residence is space that is usually much larger. - Real Estate Remodeling Works and Services. In contemporary law purchase and sale contracts can be examined in the light of three different legal systems: French, German and Soviet. Thus, if, by way of example, a house or a motor vehicle, by inheritance, will belong to several persons, each of whom will become the owner of only an ideal share or fraction, contained within a every larger one, behold, an object which would not have a comfortable division. https://imsaopedro.com.br/
Dear Jean-Baptiste Faure, 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
Nothing changed in Version: 7.3.1.0.0+ / LibreOffice Community Build ID: de15e8d4f2f2e5d10cb5d9203e51f3a28347db8d CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Ubuntu_20.04_x86-64 Calc: threaded Best regards. JBF
I guess I have to wonder what was going on when I commented quite a while back (2018-09-15 02:33:05 UTC, #16). At any rate, the bug is still there now. It MIGHT be relevant that these files are using "track changes", I suppose. I also have to say about the same as Anton (# 12). I've reported or gotten added to the tracking of several bugs. YEARS go by, and they aren't fixed or (apparently) even worked on. Yet every year I'm asked to go through the hassle of installing the latest version (losing history (that must be in the Windows registry) in the process). The bug is always still there. Several of these (this one for example) are quite serious, in terms of my ability to use LibreOffice for things I'm working on. It's quite a pain. Regarding comment # 7: Yes, it's an obvious workaround. It's also a security problem, defeating the whole purpose of encrypting documents. If the comparisons worked a LOT better, I would do it anyway. But as it is, if I'm going to do this, I save them in another format which can be compared by a simple diff. Anyway: bug is still there as of now, in: Version: 7.1.8.1 (x64) / LibreOffice Community Build ID: e1f30c802c3269a1d052614453f260e49458c82c CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
*** Bug 156187 has been marked as a duplicate of this bug. ***