Created attachment 71827 [details] Spreadsheet that fails. Problem description: Steps to reproduce: 1. Open the relevant xls file Current behavior: 1. The specified error message pop-up box appears. Expected behavior: 1. The script works as expected Operating System: Ubuntu Version: 3.6.4.3 release
By marking it as UNCONFIRMED, does that mean that the attached spreadsheet worked for you?
@ Ron, The bugzilla system starts all bugs as unconfirmed then with multiple reports or qa reproduction the issue goes to New status. I added myself to CC: as someone interested in BASIC implementation: I wanted to know if someone else fixed it and to be able to find the bug later (without assigning myself). On download+open of spreadsheet I get this warning: The numbering add-in must be loaded for optimal toolbar and numbering behavior. Please load this add-in to your Library directory. then I get the error 23 message. Definitely confirmed. If LibreOffice BASIC does not implement support the OnSheetActivate event, this could be a compile time error instead of a run-time error. Certainly the message could be more helpful. If these events are supported then that implementation appears broken (or again at least unhelpful). Either way, message needs improvement.
Thanks for the clarification. :)
Created attachment 93715 [details] bt with symbols on master On pc Debian x86-64 with master sources updated yesterday, I had a crash. I attached bt + console logs. (with 4.2 sources I also have got a crash).
** 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 (4.4.2 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Still present in 4.4.3.2 (88805f81e9fe61362df02b9941de8e38a9b5fd16).
Created attachment 115866 [details] console+bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this. I updated the bt but seems quite the same.
Stephan: could it be a Uno pb (since it appears in bt) or is it completely Basic related?
** 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
Still repro Arch Linux 64-bit Version: 6.4.0.0.alpha0+ Build ID: 37fc9f51a8de11d40632e8cda17ccf1fa4b1f503 CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 6 August 2019
It still fails in LibreOffice 6.1.5.2 on Xunbuntu 18.04. Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805 CPU threads: 6; OS: Linux 4.15; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group threaded When opening the file, it says macros must be enabled, so I click that button. Then it fails saying that TMPLTNUM.XLA does not exist. When I click ok to that, the error message "object not accessible. The object cannot be accessed due to incufficient user rights." appears. When I click ok to that, it says I must install the numbering add-in needs to be loaded. When I click ok to that, it shows the original BASIC 423 error.
(In reply to Julien Nabet from comment #8) > Stephan: could it be a Uno pb (since it appears in bt) or is it completely > Basic related? This doesn't appear to be a UNO problem. Your crash and backtrace from comment 4 and comment 7 appear to be unrelated to the problem described in comment 0 and comment 11. (And I can reproduce the recipe from comment 11 with a recent local Linux master build.)
Still reproducible in: Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 6; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
Dear Ron Johnson, 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