Bug 44540 - FILESAVE: save with password error
Summary: FILESAVE: save with password error
Status: CLOSED DUPLICATE of bug 41089
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.4.5 RC1
Hardware: Other All
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2012-01-06 10:48 UTC by Ismael Cedillo
Modified: 2012-01-10 12:50 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attached the error message tha shows the system (9.37 KB, image/png)
2012-01-06 10:48 UTC, Ismael Cedillo

Note You need to log in before you can comment on or make changes to this bug.
Description Ismael Cedillo 2012-01-06 10:48:53 UTC
Created attachment 55219 [details]
Attached the error message tha shows the system

Problem description: 

When I try to save a writer document to protect with a password, it presents an error and not save the document.

Steps to reproduce:
1. ....Any writer document is opened
2. ....In menu select <<File>>, <<Save as..>>
3. ....Check the option "Save with password"
4. ....Push <<Save>> button
5. ....See the error message

Current behavior:
Do not save with password.

Expected behavior:
Save with password to protect the content of documents

Platform (if different from the browser): 
Browser: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Comment 1 manj_k 2012-01-06 12:08:03 UTC
FILESAVE with password protection works fine with LibO 3.4.5 RC2 
[LibreOffice 3.4.5 · OOO340m1 (Build:502)]
(Writer · UI en-US · on WinXP 32b).

Thanks, already reported with 'Bug 41089 - FILESAVE: Impossible with password protection'.

*** This bug has been marked as a duplicate of bug 41089 ***
Comment 2 Ismael Cedillo 2012-01-10 09:02:30 UTC
I saw that the testes for this report were made on Windows 32b, and I really don't know if with a report for this bug in Windows-32b is enough... but I forgot to mark that it was identified on

Ubuntu 11.10
X86-64 system
and LibreOffice 3.4.5 OOO340m1 (Build:501)

Comment 3 Ismael Cedillo 2012-01-10 09:24:19 UTC
The bug was solved in the 3.4.5 RC2 build 502. 

Comment 4 manj_k 2012-01-10 12:50:32 UTC

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