|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | ScriptProviderForooRexx.oxt cannot be successfully installed with unopkg on MacOSX 3.4.0, 3.4.1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Installation | Reporter: | rony | ||||
| Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
| Status: | CONFIRMED --- | QA Contact: | |||||
| Severity: | Normal | ||||||
| Priority: | P3 | CC: | awf.aoo, jsc, rony | ||||
| Version: | 3.4.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Mac OS X, all | ||||||
| Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
| Developer Difficulty: | --- | ||||||
| Attachments: |
|
||||||
|
Description
rony
2012-07-24 18:07:10 UTC
One possible reason for this problem might be that in order to install an extensions shared, you need superuser/admin access rights. This is currently not supported by AOO outside the installer. I am more surprised that it works on Windows and Linux than that it does not work on MacOSX. See bug 119272 for another representation of this kind of problem. Andre, thank you for your feedback! However, the postflight script runs unopkg via sudo, such that all rights should be available to unopkg to create any directory or copy any files. The installation in addition adds ooRexx sample scripts to the shared AOO locations successfully. Running the unopkg command with sudo from the command line as reported, does not work either. I am pretty sure, that in the past (OOo 3.2?) the installation as a shared extension worked on MacOSX. --- Ad Linux: here running unopkg via sudo works. Ad Windows: here running elevated works. --- If there is anything else I could provide, please let me know. On the MacOSX I am using the Iceberg installer, if that makes a difference (it should not as the postflight script runs unopkg explicitly via sudo). Ah, forgot to point out: this installation is carried out under the control of the BSF4ooRexx Iceberg installer. At the point when unopkg gets invoked to install the oxt as a shared extension, the credentials are those of sudo such that all rights should be available to unopkg to do whatever it needs to do. Created attachment 79989 [details]
AOO extension (script provider for the ooRexx language)
This extension can only be installed in user mode on a MacOSX, but not in "shared" mode, even if running unopkg as superuser.
At ApacheCon Europe it has turned out that the extension in question can be successfully installed for a user. However running unopkg as sudo and trying to install in shared mode yields the reported errors/problems. The oxt-file was just uploaded, such that this can be tested without a need to install the full BSF4ooRexx package. I have installed the ScriptProviderForooRexx.oxt in a AOO 4.0 dev version on my MacOs 10.7.5 system. I installed for all users and I am in the admin group. I don't use sudo because this causes a problem with a tmp directory in the user profile. The tmp directory can't be deleted. Can you please try to install it with a user with admin rights. Or with sudo unopkg ... but then please start the office also with sudo directly after the installation. during the next office start the tmp directory gets synchronized and deleted. There is indeed room for improvements but I don't see that somebody will work on this. The whole extension deployment framework should be reworked to remove some complexity. The reported anomality when executing Rexx scripts may be linked to executing the scripts on the wrong thread, cf. <https://issues.apache.org/ooo/show_bug.cgi?id=124170> (there one finds instructions how to test this with a debug version of the oxt, that simply uses a JDialog for popups, which fails, when started on the wrong thread). A question ad your remark to restart AOO in sudo mode to have it clean up the tmp directory: how could one possibly do that from the command line? The package is added using unopkg from the command line and causes an instance of AOO to be created and lingering. If there was a command line argument to soffice for quitting AOO, then I could follow your advice. Or, is there maybe some undocumented possibility to do that? If so, then I would be able to follow your advice. |