https://bugs.documentfoundation.org/show_bug.cgi?id=168062

            Bug ID: 168062
           Summary: Empty document is opened if Set permission password is
                    set
           Product: LibreOffice
           Version: 25.8.0.4 release
          Hardware: All
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
In export to PDF if "Set permission password" is set then when exported
document is opened and correct password entered, empty document is displayed
instead of text at export time.

Steps to Reproduce:
1. Open LibreOffice Writer.
2. Type: test
3. File | Export As | Export as PDF
4. General tab set General | PDF Version to PDF 2.0.
5. General tab check "Hybrid PDF (embed ODF file)"
6. Security tab | Set Password button.
7. "Set open password" set to some password and the same for "Confirm" field.
8. "Set permission password" and set some password and the same for "Confirm"
field and OK button.
9. Export button set some file name and Export button.
10. Close down ODF document and don't save it.
11. Open exported PDF file.
12. Enter Password dialog appears. Type in password and OK.

Actual Results:
Empty document appears.

Expected Results:
I except to get text from step 2 displayed.


Reproducible: Always


User Profile Reset: No

Additional Info:
Additionally 1:
I have opened Firefox and File | Open and point to pdf file, typed in password
and document is correctly displayed.

Additionally 2:
Repeat the test, but skip step 8 and everything works fine in step 13 text is
displayed as expected.

Help | About:
==========================
Version: 25.8.0.4 (X86_64) / LibreOffice Community
Build ID: 48f00303701489684e67c38c28aff00cd5929e67
CPU threads: 16; OS: Linux 6.14; UI render: default; VCL: gtk3
Locale: sl-SI (en_US.UTF-8); UI: en-US
Flatpak
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to