From http://bugs.debian.org/608732: "[...] a macro in an extension i'm working at crashes libreoffice. i will attach the extension and instructions to reproduce problem." and "this extension i'm making responds ok on ooo3.2.1 but crashes on lo3.3.0rc[12]. the offending macro: dynamicDialog/createDialog. it fails to run, and lo crashes on exit. i have a quite similar script in .../user/Scripts/python that does run, but lo also crashes on exit." unfortunately no more info, except the attachement, which I am also going to attach here.
Created attachment 41801 [details] the extension
I can't install this extension; I get an error dialog from the Extension Manager: (com.sun.star.uno.RuntimeException) { { Message = "<type 'exceptions.AttributeError'>: 'module' object has no attribute 'writeRegistryInfo', traceback follows\X000a /data/opt/.../pythonloader.py:138 in function writeRegistryInfo() [ return mod.writeRegistryInfo( self.ctx.ServiceManager, regKey )]\X000a Context = (com.sun.star.uno.XInterface )@0 } } (manually transcribed FWIW) ;-)
Well; the built-in python sample runs fine, so it is not some super-profound problem. Similarly - I installed the ooconfig extension: http://wiki.services.openoffice.org/wiki/OoConfig which (it seems) is under-maintained. That failed to install any menu items I could use - but at least installed without errors [ it appears to register its component properly ]. So - this really looks like some error in the developers' component to me.
CC
no stack / valgrind trace (as asked), supplied extension will not install - missing the registration hooks it needs, other python extensions install, and the included python sample works fine so ... un-marking as a blocker.
The extension in the attachment installs with an error on WinXP+LibO3.3.orc3.
Created attachment 42184 [details] extension, that can't be installed on Windows with LibO/OOo 3.3.0 rc3/rc9 Try also this extension extracted from here http://wiki.services.openoffice.org/wiki/Extensions_Packager#A_sophisticated_extension (see attachment) With OOo3.3.0rc9 and LibO3.3.0rc3 on Windows it installs with errors. On Linux all is fine. Also , on Windows, with OOo3.3.0rc9, it's impossible to run Python macro by going to menu Tools/Macros/Organize macros.../Python - choose macro - Run. With LibO there are no preinstalled Python macroses, not so easy to check. But the extension in the attachment have Java, JavaScript, Python nd Basic macroses. After installing it, restart, open Writer, go to Tools/Add-ons/Calling scripts menu. But the problem is, that yo can't install it on Windows XP and Vista (they are tested).
Other python extensions having <manifest:file-entry manifest:full-path="OptionsDialogHandler.py" manifest:media-type="application/vnd.sun.star.uno-component;type=Python"/> in manifest.xml install fine. (MRI, DefaultBrowser etc) But if the extension has <manifest:file-entry manifest:media-type="application/vnd.sun.star.framework-script" manifest:full-path="RESHETEVAAutoContractScripts/"/> in manifest.xml - the installation fails. I.e., python scripts can't be registered. Only Python uno-components can. (imho, this is a stopper)
Maybe this has something to do with http://qa.openoffice.org/issues/show_bug.cgi?id=116035 ? One person says the problem with python scripts is solved if msvcr90.dll and the manifest is copied to the python folder (?)
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
In version 3.5.0 problem still exist?
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian