When setting a document (any type) to "read only"-status by using: * dispatcher.executeDispatch(document, ".uno:EditDoc", "", 0, Array()) or * the Icon in the menu-bar "standard" starting any Macro will throw following Exception: com.sun.star.uno.RuntimeException/home/fstrba/cvs/ooo-build/build/libreoffice-3.3.2.2/package/source/xstore/xstorage.cxx: :4877 ... in a message box. The error can not be cought by "on error goto" since it happens before the macro starts. Macros were started by * menu (extras/macros/run macro) by * button in the document * Icon in a menu-bar with linked macro Macros always run when started with F5 from the BASIC-IDE! LibreOffice 3.3.2 OOO330m19 (Build:202) tag libreoffice-3.3.2.2
Ubuntu 10.04 & 10.10 WinXP SP2
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Hi, Confirmed on: /daily/master/Linux-rpm_deb-x86_64@46-TDF/2014-11-28_00.50.11 /daily/master/Win-x86@51-TDF/2014-11-28_08.54.54
Created attachment 121380 [details] stack trace, m_pImpl == 0 in OStorage::getPropertyValue()
*** Bug 89470 has been marked as a duplicate of this bug. ***
** 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.6 or 5.2.3 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-20170103
Created attachment 131425 [details] Test document of the bug.
Tested on LibreOffice 5.1.6.2 (Windows 7). This bug is present. I wanted a functionality in a LibreOffice based application not possible due to this bug. I have created and attached a test document. Download the document and press the button "Change mode" that executes this macro: sub changemode dim oDocument as object dim oDispatcher as object oDocument = ThisComponent.CurrentController.Frame oDispatcher = createUnoService("com.sun.star.frame.DispatchHelper") oDispatcher.executeDispatch(oDocument, ".uno:EditDoc", "", 0, Array()) end sub After this the bug is manifested by pressing the button "Test".
*** Bug 103297 has been marked as a duplicate of this bug. ***
*** Bug 59670 has been marked as a duplicate of this bug. ***
Tested on development version 5.4.0.0 of date 2017-02-23. The bug IS NOT present. I will locate in which version is corrected.
(In reply to Luis from comment #11) > Tested on development version 5.4.0.0 of date 2017-02-23. > The bug IS NOT present. > I will locate in which version is corrected. Thanks, Luis. If the bug is not in 5.3, I think nothing further needs to be done. Closing as WFM.
(With the random builds I have lying around on my Linux box, I can reproduce with attachment 131425 [details] in a 5.1 and a 5.2 build, but not with a recent master towards 5.4, so this may have been fixed meanwhile.)
Bug present in 5.2.4.2
Tested in 5.2.5.1 (Windows 8) -> Bug present. Tested in 5.3.0.3 (Windows 8) -> Bug NOT present
Improperly I set status to resolved-fixed by mistake. Changed status to resolved-worksforme.