Bug 147979 - "Record changes" status changed when "Protect" changes
Summary: "Record changes" status changed when "Protect" changes
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: File-Properties
  Show dependency tree / graph
 
Reported: 2022-03-14 08:31 UTC by Po-Yen Huang
Modified: 2025-01-12 03:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Po-Yen Huang 2022-03-14 08:31:47 UTC 
Description:
In "Files" > "Properties" dialog, "Security" tab, "Record changes" option will change when "Protect" option changes.

Steps to Reproduce:
1. Open "Files" > "Properties" dialog
2. Click "Security" tab
3. Click "Protect" button
4. Type same password in "Password" and "Confirm" boxes in "Protect" dialog and click OK

Actual Results:
"Record changes" turns on when "Protect" enabled.

Expected Results:
"Record changes" remains the same, no matter "Protect" is changed.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 7.3.1.3 / LibreOffice Community
Build ID: 30(Build:3)
CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+xcb)
Locale: zh-TW (zh_TW.UTF-8); UI: zh-TW
7.3.1-1
Calc: CL
Comment 1 Indu 2022-04-06 01:33:34 UTC 
Hello!
Curious question, where did you get the reqs. for Expected Results?
Comment 2 Indu 2022-04-06 01:33:55 UTC Comment hidden (obsolete)
Comment 3 Po-Yen Huang 2022-04-06 06:40:48 UTC 
(In reply to Indu from comment #1)
> Hello!
> Curious question, where did you get the reqs. for Expected Results?

From our users, and we also think this behavior is a little weird.
Comment 4 raal 2022-05-27 21:47:38 UTC 
Reproducible in 7.4 and Version 4.1.0.0.alpha0+.
Comment 5 QA Administrators 2025-01-12 03:13:23 UTC 
Dear Po-Yen Huang,

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