Bug 129844 - comparing two password protected documents always gives error "wrong password"
Summary: comparing two password protected documents always gives error "wrong password"
Status: RESOLVED DUPLICATE of bug 41544
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.4.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-06 21:37 UTC by Oliver Grimm
Modified: 2020-01-17 17:53 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Grimm 2020-01-06 21:37:06 UTC
Description:
Comparing two ods files via menu "edit | changes | compare document" results in an error message if both documents are password protected (internal libreoffice password protection).

Steps to Reproduce:
1. create a new spreadsheet file (1) and save with password
2. create another new spreadsheet file (2) and save with password
3. close both files
4. open (1)
5. select "edit | changes | compare document" from main menu
6. select file (2) in the file chooser
7. provide the correct passwords upon request

Actual Results:
yields an error message "reading error. a wrong password has been set" (translated from German)

Expected Results:
file (2) is opened and file comparison is completed


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.3.4.2.0+
Build-ID: 1:6.3.4-2
CPU-Threads: 2; BS: Linux 5.3; UI-Render: Standard; VCL: kde5; 
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded

Comparing two files without password works just fine here.
Opening both password protected files respectively works fine, too.
Comment 1 Julien Nabet 2020-01-16 22:06:49 UTC
On pc Debian x86-64 with master sources updated today, I could reproduce this.
Comment 2 Timur 2020-01-17 17:53:52 UTC
Rule of thumb is search before reporting and confirming. 
Otherwise we are all losing our time. 
And this looks like a duplicate.

*** This bug has been marked as a duplicate of bug 41544 ***