Using the LibreOffice MSI package for LibreOffice 4.0.4, 32 Bit Windows 7 Pro DE I made the following observations: * when Base is installed as the only component, it is not possible to start it (when the exe is launched, nothing happens, no splash screen etc.) * when I add Writer to the installation, Base is working Does Base depend on Writer (shared libraries?) and should this be fixed? Kind regards, Matthias
*** This bug has been marked as a duplicate of bug 33798 ***
*** Bug 68407 has been marked as a duplicate of this bug. ***
I can confirm this bug with Version 4.1.2.3 on Win 7. But it works for me with Version 4.0.0.3. According to bug 68407 the bug exists in all later versions, i.e. this bug is a regression to Version 4.0.0.3. Furthermore I performed some test cases according bug 33798. That bug still exists in both versions (4.0.0.3, 4.1.2.3). Hence this bug (67130) can't be a duplicate of bug 33798. Thus status unduplicated and set to Confirmed. ----- My test procedure: For both test cases first I deinstalled LibreOffice and deleted/removed the user profile. Then: Test case in order to reproduce bug 67130: [1] Start a new installation of LibreOffice. [2] Select the custom installation [3] Deselect "LibreOffice Programm Modules" [4] Select "LibreOffice Base". (No other changes in Custom dialogues) [5] Perform the installation. [6] Try to start LibreOffice. Result: Works for me with Version 4.0.0.3, fails with Version 4.1.2.3. Test case in order to reproduce bug 33798: [1] Start a new installation of LibreOffice. [2] Select the custom installation [3] Deselect "LibreOffice Programm Modules" [4] Select "LibreOffice Writer". [5] Select "LibreOffice Calc" (No other changes in Custom dialogues) [6] Perform the installation. [7] Try to start LibreOffice. It starts(!) with both versions (4.0.0.3, 4.1.2.3), but in both version only Writer can be used. It is not possible to create a new spreadsheet. ---- Hence the same problem occurs also with Draw (bug 68407) I changed the subject of this bug. To my opinion this bug is at least a major problem and should be fixed soon. Hence "Importance" changed. Suppose a new user only wants to use one component and then is not able to install LibreOffice. In most times she/he will put aside LibreOffice. Thus a candidate for a MAB?
Subject changed again hence LibO also does not start if two LibO components are installed under certain conditions. This case occurs if you like to install only Calc and Draw and therefore deselect Writer, Impress, Base and Math.
*** Bug 70369 has been marked as a duplicate of this bug. ***
The culprit is share/registry/librelogo.xcd. If it is there, and writer.xcd is not there, the LibreOffice will not start.
So, to make it clear, if you for whatever reason do not want to install all LibreOffice program components, and if you omit Writer from the mix, then do not install LibreLogo, which is a Writer toolbar. This is a workaround for this very bug. I have had enough issues from this behavior, and I do not think that it makes any sense to install only a limited set of program components. Therefore I removed this optionality from the Windows installer UI in master. https://gerrit.libreoffice.org/gitweb?p=core.git;a=commit;h=32bbc8d9d84e56ef0dbc34b2a6f3057e3274a357 Windows installer still has too many options compared to Mac, where there isn't any.
(In reply to comment #7) > I have had enough issues from this behavior, and I do not think that it > makes any sense to install only a limited set of program components. > Therefore I removed this optionality from the Windows installer UI in master. From your commit http://cgit.freedesktop.org/libreoffice/core/commit/?id=32bbc8d9d84e56ef0dbc34b2a6f3057e3274a357: "It is hard to imagine a user who insists on having just Writer and Calc but not Impress and Draw, etc." Maybe on Linux, but it is not so hard on Windows. If a company have Office Basic installations without PowerPoint, then it would like to install just Impress and not a whole package. Such users do not need Writer, Calc, LibreLogo etc. Hope this change will be discussed more and maybe reverted, as it will complicate life of enterprise admins in companies which do not want to clutter install program base with unwanted parts of a suite. It would be better to fix installer/suite dependencies once and for all and give user proper error messages instead of crashing or not running the app at all. Fixing such problems by removing an installer feature is not a way to go imho.
(In reply to comment #8) > From your commit > http://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=32bbc8d9d84e56ef0dbc34b2a6f3057e3274a357: > "It is hard to imagine a user who insists on having just Writer and Calc but > not Impress and Draw, etc." > > Maybe on Linux, but it is not so hard on Windows. If a company have Office > Basic installations without PowerPoint, then it would like to install just > Impress and not a whole package. Such users do not need Writer, Calc, > LibreLogo etc. > Hope this change will be discussed more and maybe reverted, as it will > complicate life of enterprise admins in companies which do not want to > clutter install program base with unwanted parts of a suite. > It would be better to fix installer/suite dependencies once and for all and > give user proper error messages instead of crashing or not running the app > at all. > Fixing such problems by removing an installer feature is not a way to go > imho. Did you read the first part of the commit message? Unlike Microsoft Office, LibreOffice is not a collection of individual applications. As a systems administrator, you can still disable any feature from the command line when you deploy LibreOffice to users, or you can edit the .msi, or you can remove unwanted shortcuts from users' start menu. My first thought was to fix the dependencies in installer. I spent 3 hours on it without success. If anyone knows how to fix it, I'm interested. No developer/build environment is required, just Orca MSI editor and lot of patience.
(In reply to comment #9) > Did you read the first part of the commit message? Unlike Microsoft Office, > LibreOffice is not a collection of individual applications. As a systems Microsoft Office also is not a collection of individual applications. It seems they just have better dependency tree or error messages in the suite. > administrator, you can still disable any feature from the command line when > you deploy LibreOffice to users, or you can edit the .msi, or you can remove > unwanted shortcuts from users' start menu. So, now every small business company IT administrator have to learn msi magic (with its own problems) to achieve what was clickable a release earlier... > My first thought was to fix the dependencies in installer. I spent 3 hours > on it without success. If anyone knows how to fix it, I'm interested. No > developer/build environment is required, just Orca MSI editor and lot of > patience. I think you should start with such help request on MLs or file more bugs for those who can pick them up for fixing and not remove a feature which is used just because you can't fix it in 3 hours. Seems this should be discussed elsewhere to not clutter this report and got more attention of those who can help you fix the real problem.
*** Bug 71086 has been marked as a duplicate of this bug. ***
(In reply to comment #7) > I have had enough issues from this behavior, and I do not think that it > makes any sense to install only a limited set of program components. > Therefore I removed this optionality from the Windows installer UI in master. > > https://gerrit.libreoffice.org/gitweb?p=core.git;a=commit; > h=32bbc8d9d84e56ef0dbc34b2a6f3057e3274a357 @Andras: In which LO version this change will be available?
(In reply to comment #12) > @Andras: In which LO version this change will be available? 4.2.0
The removal of the optionality to install not all LibreOffice components has not been regarded in the Release Notes of version 4.2 yet (1). To my opinion it should be mentioned under the point "Feature Removal". (1) https://wiki.documentfoundation.org/ReleaseNotes/4.2
Verified with version 4.2.4 and Win 7. Optionality to install not all components is removed. Works as described by Andras. Hence status set to CLOSED.
*** Bug 80297 has been marked as a duplicate of this bug. ***
Hello, As reporter for bug #82297, and as a not so "small business company IT administrator" but with a small IT team (2 guys in fact) I need to enter the discussion about the new MSI behavior. If we consider that full installation is the only "good" way to go with LibreOffice 4.2, then there is a problem with upgrade process that still only upgrade previously installed components but doesn't install other available components by default. Bfoman said "If a company have Office Basic installations without PowerPoint, then it would like to install just Impress and not a whole package. Such users do not need Writer, Calc, LibreLogo etc.". This is what we did in fact : we manually installed Draw and Impress to a lot of computers because we couldn't pay for MS Visio and Powerpoint (and that it was a good way to introduce opensource and talk about this with users). It was release 3.6.5. Recently, we tried to upgrade to release 4.1.xx on Win XP and 7 with or without success depending on the computer, but we didn't find the reason. I know a lot of companies that wouldn't have tried more than 1 day before calling an MS reseller and asked for MS Office licences... We then decided not to upgrade LibreOffice at all. :-/ Somes days ago, I tried the newest release 4.2.4.2, with the same problem but I finally understood that the problem only appears when upgrading from a partial installation of LibreOffice. Now, I need to deploy LibreOffice to 250 computers. My goal is to use a Software Installation Group Policy. This is not a script based process, and it does not allow to use command line parameter : the MSI is supposed to behave the way you want, or you can tweak the MSI tables, or you can provide a MST file to specify necessary parameters. First solution : MSI behavior => NOK => the MSI upgrade process does not install missing components that where not previously installed. Therefore, the new upgraded installation does not work anymore... Second solution : tweak MSI => OK but... => You can add an "ADDLOCAL" parameter with "ALL" as a value in the PROPERTY table. This method seems to work but MS explain that it should be avoid (don't ask me why... I am not an MSI guru :)) (source : http://msdn.microsoft.com/en-us/library/aa367536%28v=vs.85%29.aspx) Third solution : MST file => not tried... is there a way to create this MST file with expected parameter for a "force all components" upgrade process ? The path to upgrade isn't really clear for MS network sys admins... Would it be possible to change the MSI default upgrade behavior to not only upgrade already installed components but also install the other available components (nearly equivalent to uninstall existing release and install full new release) ? Should this be transformed into a feature request ? Regards, Olivier.
Sorry, I mean bug #80297, not #82297.
Migrating Whiteboard tags to Keywords: (regression) [NinjaEdit]