Created attachment 139333 [details] Screenshot of the failed extension installation We have an internal configuration extension, which we install via SCCM using unopkg.com If LO is running, unopkg fails to install the extension. This is rather annoying, as it is possible to install extensions interactively via the GUI (obviously). So why should it be impossible via command line? The screenshot shows an example of this behavior, I think it should be reproducible with any extension (also sorry for the Hungarian UI): - First time LO does not run, the command runs successfully, because the extension is not yet installed. - Second time LO does not run, the command fails to install the extension because it is already installed. - Third time I started LO, the command fails to install the extension. This time not because it is already installed, but because of an "unknown error".
Note: while the --shared options description explicitly says it works only when no Office processes are running, this time I did not use that.
@Stephan, I thought you could be interested in this issue...
Works fine at least with my local Linux master build. Needs investigation why it fails for you on Windows.
Dear Gabor, Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Dear Gabor Kelemen, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Gabor Kelemen, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp