Bug 134471 - "Application.CommandBars("Ply").Enabled = True" VBA error
Summary: "Application.CommandBars("Ply").Enabled = True" VBA error
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
6.4.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Macro-VBA
  Show dependency treegraph
 
Reported: 2020-07-03 09:04 UTC by johnks
Modified: 2022-07-09 03:35 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
xlsm file containing problem vba (162.99 KB, application/vnd.ms-excel.sheet.macroEnabled.12)
2020-07-03 09:04 UTC, johnks
Details

Note You need to log in before you can comment on or make changes to this bug.
Description johnks 2020-07-03 09:04:17 UTC
Description:
BASIC runtime error.
'1'

Type: com.sun.star.uno.DeploymentException
Message: component context fails to supply singleton com.sun.star.ui.theModuleUIConfigurationManagerSupplier of type com.sun.star.ui.XModuleUIConfigurationManagerSupplier

Steps to Reproduce:
vba containing the code 
Application.CommandBars("Ply").Enabled = True

throws the error and does not work. calc shifts user to libreoffice basic with this error and refuses to go to actual document. Further, does not allow user to easily close the file 


Actual Results:
https://stackoverflow.com/questions/24540929/commandbarsply-wont-reset-on-workbook-beforeclose-vba-excel

Expected Results:
vba should execute as it works in excel


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.4.2.2
Build ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: kf5; 
Locale: en-IN (en_IN.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 johnks 2020-07-03 09:04:57 UTC
Created attachment 162602 [details]
xlsm file containing problem vba
Comment 2 Julien Nabet 2020-07-03 10:55:32 UTC
On pc Debian x86-64 with master sources updated today + authorize macro, the first error popup message I got is:
"BASIC runtime error.
'423'
ExecuteExcel4Macro

(Line showed is line 13, first line from Workbook_Open method)

Then I can indeed see your message
Comment 3 Julien Nabet 2020-07-03 10:57:02 UTC
I noticed this on console:
warn:scripting:701294:701294:scripting/source/basprov/basprov.cxx:329: LibraryName VBAProject is part of the url VBAProject.ThisWorkbook.Workbook_Open

Don't know if it's related.
Comment 4 johnks 2020-07-03 12:33:03 UTC
yes. that error too. i was going to add a new bug report for that or can this bug report will suffice for both?
Comment 5 Julien Nabet 2020-07-03 12:42:57 UTC
For the moment, I don't think it needs a new bugtracker but I may be wrong.
Comment 6 QA Administrators 2022-07-09 03:35:08 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