To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70147
------- Additional comments from [EMAIL PROTECTED] Sat Apr 28 22:00:53 +0000 2007 ------- The inconsistent structure leads to an annoying errormessage (something like "basic: script.xlc not found") when a normal user starts OOo and performes some very simple harmless things. In most cases, the action the user wants to do is getting chanceled and could not be performed until the structure gets repaired by the admin manually. This could be reproduced on user side doing the following steps: 1) bring OOo in an inconsistent state as described above. 2) switch to a normal user account 3) Start OOo-writer and call "Tools->Customize..." 4) now try to add a menuitem or a shortcut that calls a basic macro. You will see that this step should NOT be possible due to the upcoming error message (described above). So it is possible to bring OOo into an inconsistent state where users can't performs things they want to do and need to do where assistence by the admin is required. This is no problem for only one user on one computer, but it is a problem for large companies with a lot of computers/users when distributing a custom uno-package that contains basic-macros. Another thing is that the conditions for getting this inconsistency are complied *by default* on all windows systems as the quickstarter-process is enabled by default. The quickstarter also behaves as a process that blocks ressources that "unopkg remove ... --shared" wants to use. Admins very often forget to close the quickstarter before upgrading a custom uno-package and will trigger the above situation undeliberate. Upgrading uno-packages that contain basic macros should be as easy as upgrading uno-packages without basic macros. Our production component for example contains complex jar-files and custom services (rdb-file) and the basic-code is only a minor part of the component. All these other elements don't have problems with the running quickstarter, wheras the view lines of basic code contained leed to this issue. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
