Problem description: Opening Excel spreadsheet with VBA macros results in message - BASIC runtime error '423' find control. Macro attempts to call a DeleteControl but apparently fails. Works in Excel fine. Steps to reproduce: 1. Open Excel file in LibreOffice 2. Allow Macros 3. Error message pops up on both open of file and close. Current behavior: Error message pops up Expected behavior: Proper macro call and no error message Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.15 Safari/536.5
Could you please attach a file, in which the problem occurs?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO
Created attachment 99432 [details] xls spreadsheet This file causes the BASIC runtime error. '423' FindControl
I just attached a document that causes this error in LibreOffice Version: 4.2.3.3 Build ID: 420m0(Build:3) on Ubuntu 14.04 x64. Not sure if its appropriate to reopen this old bug but it appears to be the exact same error. I'm happy to help in any way I can. What does the error even mean?
Never confirmed by QA team - moving to UNCONFIRMED to get confirmation. Thanks
(In reply to Elias K Gardner from comment #4) > Created attachment 99432 [details] > xls spreadsheet > > This file causes the BASIC runtime error. '423' FindControl 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 Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
Added original file dropbox URL - https://www.dropbox.com/s/gbgzfte6j4jo1mb/Financials%20Projections%20Template.xls?dl=0
(In reply to brajalle from comment #8) > Added original file dropbox URL - > https://www.dropbox.com/s/gbgzfte6j4jo1mb/ > Financials%20Projections%20Template.xls?dl=0 Same message: 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 Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear QA, I am not sure how I am related to the bug and the bug reporter. I have stopped using VBA-scripts some years ago because I generally expected it to not work. Furthermore I do not need VBA-scripts. thank you for attention. (In reply to QA Administrators from comment #10) > ** Please read this message in its entirety before responding ** > > 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 on a currently supported version of > LibreOffice > (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ > > If the bug is present, please leave a comment that includes the version of > LibreOffice and > your operating system, and any changes you see in the bug behavior > > If the bug is NOT present, please set the bug's Status field to > RESOLVED-WORKSFORME and leave > a short comment that includes your version of LibreOffice and Operating > System > > 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) > > http://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: > http://webchat.freenode.net/?channels=libreoffice-qa > > Thank you for helping us make LibreOffice even better for everyone! > > Warm Regards, > QA Team > > MassPing-UntouchedBug-20160920
(In reply to Nico from comment #11) > Dear QA, > > I am not sure how I am related to the bug and the bug reporter. I have > stopped using VBA-scripts some years ago because I generally expected it to > not work. Furthermore I do not need VBA-scripts. You are related to it, because you added yourself to the CC list on 2015-08-24 14:01:39
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still reproducible. Version: 6.2.0.0.alpha0+ Build ID: 6dacf9ec5455bdad82e78470a1a7cb6d2271bec7 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: threaded from yesterday
Dear brajalle, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/20bca05a8e5a07c21451e4c62064d1a5680611d9 crashtesting: null deref on import of fdo48634-1.xls It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
On pc Debian x86-64 with master sources updated today, I could reproduce this. I still got the same error message as comment 7 and noticed these logs on console: warn:sc:11440:11440:sc/source/filter/excel/xlroot.cxx:157: XclRootData::XclRootData - cannot get output device info com.sun.star.uno.RuntimeException message: invalid attempt to assign an empty interface of type com.sun.star.frame.XFrame! /home/julien/lo/libreoffice/include/com/sun/star/uno/Reference.hxx:105 warn:sfx.control:11440:11440:sfx2/source/control/dispatch.cxx:1206: Childwindow slot missing: 25917 warn:sfx.control:11440:11440:sfx2/source/control/dispatch.cxx:1206: Childwindow slot missing: 25917 warn:i18nlangtag:11440:11440:i18nlangtag/source/languagetag/languagetag.cxx:1648: LanguageTag::getRegionFromLangtag: pRegionT==NULL for 'eo-EO' warn:i18nlangtag:11440:11440:i18nlangtag/source/languagetag/languagetag.cxx:1648: LanguageTag::getRegionFromLangtag: pRegionT==NULL for 'eo-EO' warn:legacy.tools:11440:11440:svx/source/form/fmvwimp.cxx:437: FmXFormView::~FmXFormView: Window list not empty! warn:scripting:11440:11440:scripting/source/basprov/basprov.cxx:309: LibraryName VBAProject is part of the url VBAProject.ThisWorkbook.Workbook_Open warn:legacy.osl:11440:11440:sfx2/source/control/shell.cxx:209: SfxShell::SetUndoManager: exchanging one non-NULL manager with another non-NULL manager? Suspicious!
Dear brajalle, 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
excel spreadsheet won't open word document won't open