Created attachment 73393 [details] a simple bugged document Hello, I encounter a strange bug involving BASIC macro, event and protected documents with password. I attached a simple writer documents that bug. * activate the macros in your security settings * open the document * unlock the document (click on "Edit File") * close the document or libreoffice → com.sun.star.uno.RuntimeExceptionScriptProtocolHandler::createScriptProvider(), /home/max/libreoffice/nightly_build/package/source/xstor/xstorage.cxx:5069: The document contains : * a simple text "test", which as nothing to do with the bug * a macro : "Standard.test.aaa" which call msgbox("aaa"). The msgbox function as nothing to do with the bug. * events "Open Document" and "Document is going to be closed" are linked to the "Standard.test.aaa" macro. Interesting facts : * this bug is also present on 3.6 version. * no bug on documents protected without password (documents which are just open in read-only) * no bug if the document is modified (saved or not) before closing * if the "Open Document" event link is removed the bug only appear the second time the document is closed (without restarting libreoffice) * after unlocking the document, try "Tool → Macros → run Macro", the document macro isn't present and libreoffice debug output show : warn:legacy.osl:26473:1:/home/max/libreoffice/nightly_build/scripting/source/provider/BrowseNodeFactoryImpl.cxx:355: caught an exception! in function:com::sun::star::uno::Sequence<com::sun::star::uno::Reference<com::sun::star::script::browse::XBrowseNode> > browsenodefactory::{anonymous}::getAllBrowseNodes(const com::sun::star::uno::Reference<com::sun::star::uno::XComponentContext>&) type: com.sun.star.uno.RuntimeException message: unsatisfied query for interface of type com.sun.star.frame.XModel! Does anyone have an idea ? Regards
I forgot to give the password of the document : test
I'm not following the steps. I can open the file without a password but it opens read-only, then I don't have an "edit file" option. Can you give me a bit more detail about how to reproduce this issue. Also does it exist with 3.6? Thanks!
What do you mean with "→ com.sun.star.uno.RuntimeExceptionScriptProtocolHandler::createScriptProvider(), /home/max/libreoffice/nightly_build/package/source/xstor/xstorage.cxx:5069:"? Does LO print that on stdout/stderr (but otherwise work fine), or does it crash there, or...?
Created attachment 73441 [details] error when closing the document
Created attachment 73442 [details] Tool → Macros → run Macro
Created attachment 73443 [details] how to unlock the document
> I can open the file without a password but it opens read-only It's the edit mode that is protected. sorry, I didn't mention it in my first post. > I don't have an "edit file" option I added a screenshot showing the icon for unlocking the document. > Also does it exist with 3.6? Yes > What do you mean with "→ com.sun.star… > Does LO print that on stdout/stderr (but otherwise work fine), or does it crash there, or...? LO (compiled with debug flags) print it on stdout/stderr, it doesn't crash. Also the document macro aren't there. I added a screenshot showing what happen when I go to "Tool → Macros → run Macro" after unlocking the document. I also added a screenshot showing the error I get when I close the document after unlocking it.
As it exists in 3.6 I am changing the version to reflect this, version is the oldest version that the bug is seen on. We use comments to reflect tests done on later versions. I'll try to find someone to confirm this behavior. Thanks!
Reproducible with Version: 4.4.0.0.alpha0+ Build ID: 7d06a0601ddccc50185ea97fddcdf2ea39299096 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-07-28_06:17:50 error msgbox after close LO: com.sun.star.uno.RuntimeExceptionScriptProtocolHandler::createScriptProvider(), Reproducible with version LibreOffice 3.5.0 error msgbox: com.sun.star.uno.RuntimeExceptionScriptProtocolHandler::createScriptProvider(),xstorage.cxx:5098;
** 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.0.0.5 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-09-03
** 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
*** This bug has been marked as a duplicate of bug 45313 ***