Bug 155428 - thisworkbook.unprotect password shows "Basic runtime error '1'
Summary: thisworkbook.unprotect password shows "Basic runtime error '1'
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
6.2.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Macro-VBA
  Show dependency treegraph
 
Reported: 2023-05-21 17:49 UTC by johnks
Modified: 2025-07-06 03:10 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screenshot of error (170.32 KB, image/png)
2023-05-21 17:49 UTC, johnks
Details

Note You need to log in before you can comment on or make changes to this bug.
Description johnks 2023-05-21 17:49:08 UTC
Description:
Basic runtime error 

'1'

an exception occured.

message: file is already unprotected at......




Steps to Reproduce:
1. download https://bugs.documentfoundation.org/attachment.cgi?id=187420

and follow steps mentioned in https://bugs.documentfoundation.org/show_bug.cgi?id=155427#c0
2. try to close LO (software)
3. Basic runtime error '1'
would show up

Actual Results:
"file is already unprotected" msgbox shows up. cancelling that shows the normal close dialog

Expected Results:
no error should show up


Reproducible: Always


User Profile Reset: No

Additional Info:
Additional Info:
Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Flatpak
Calc: threaded
Comment 1 johnks 2023-05-21 17:49:29 UTC
Created attachment 187422 [details]
screenshot of error
Comment 2 Xisco Faulí 2023-05-22 09:47:15 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 3 johnks 2023-05-22 09:52:13 UTC
(In reply to Xisco Faulí from comment #2)
> Thank you for reporting the bug. Please attach a sample document, as this
> makes it easier for us to verify the bug. 
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' once the requested document is provided.
> (Please note that the attachment will be public, remove any sensitive
> information before attaching it. 
> See
> https://wiki.documentfoundation.org/QA/
> FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help
> on how to do so.)

https://bugs.documentfoundation.org/attachment.cgi?id=187420

do i have to reupload the file for different bugs again and again?
Comment 4 Buovjaga 2023-07-06 12:48:11 UTC
Reproduced.

Some quick tests with older versions: I see the same behaviour in the oldest of 6.2 bibisect repository. 5.2 doesn't show any errors upon opening, but maybe it doesn't even support the macro methods?

Arch Linux 64-bit, X11
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e5e324a3420fc74fc147601bb125421e87060d93
CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 6 July 2023
Comment 5 QA Administrators 2025-07-06 03:10:49 UTC
Dear johnks,

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