Problem description: Steps to reproduce: [1] Deinstall your current version of LibreOffice. [2] Start a new installation of LibreOffice. [3] Select the custom installation and deselect all components without Draw. [4] Perform the installation. [5] In order to get clean test conditions delete or rename your LibreOffice user profile. [6] Try to start LibreOffice. It does not work. One or two seconds it seems that LO will start, but it did not. I tried it via the desktop symbol, the start menu (also only Draw) and directly from the installation folder (soffice.exe). I tried different LibreOffice versions. It works for me in Version 3.6.7 and 4.0.0. In all later release versions it does work. → Regression! I suppose it also does not work with version 4.0.5 rc2. I have not tested this yet, but I will do this soon. My System: Win 7 32 Bit. According a user on the German mailing list, the problem occurs also with Win 7 64Bit. In bug 67130 it is reported that Base does not start if it is the only installed component. Hence that bug is quite similar I doubt that bug 67130 is a duplicate of bug 33798. I prioritized this bug to Major, because users who use this kind of installations are not able to use versions later than version 4.0.0. On the other hand the installation of the whole package is a workaround. Operating System: Windows 7 Version: 4.1.0.4 release Last worked in: 4.0.0.3 release
Bug tested with LO version 4.0.5 rc2. Bug still exists.
Yesterday (September 10th 2013) I made a clean install of "LibreOffice Windows, version 4.1.1, Swedish", deselecting all components but "Calc". (On a windows 7, with all security stuff turned on – not my own computer.) The result was the same as described above. The mousepointer is "spinning" for a couple of seconds, but nothing more happens.
(In reply to comment #0) > ... > > In bug 67130 it is reported that Base does not start if it is the only > installed component. Hence that bug is quite similar I doubt that bug 67130 > is a duplicate of bug 33798. > > ... I think too that Bug 68407 and Bug 68407 are the same issue, while IMHO Bug 33798 is a different problem.
(In reply to comment #3) >... > I think too that Bug 68407 and Bug 68407 are the same issue, while IMHO Bug > 33798 is a different problem. sorry, I meant Bug 68407 and Bug 67130
(In reply to comment #4) > (In reply to comment #3) > >... > > I think too that Bug 68407 and Bug 68407 are the same issue, while IMHO Bug > > 33798 is a different problem. > > sorry, I meant Bug 68407 and Bug 67130 Just a question: why do you think bug 33798 is a different problem (because it's about writer & calc?)? Otherwise bug 67130 is also wrongly marked as a dupe of bug 33798. Lets mark this bug as dupe of bug 67130 and eventually unduplicate that bug from 33798 if it turns out it's not a duplicate. Kind regards, Joren *** This bug has been marked as a duplicate of bug 67130 ***
(In reply to comment #5) > Just a question: why do you think bug 33798 is a different problem (because > it's about writer & calc?)? Explanation see bug 67130. > Otherwise bug 67130 is also wrongly marked as a dupe of bug 33798. To my opinion this is indeed the case. > Lets mark this bug as dupe of bug 67130 and eventually unduplicate that bug > from 33798 if it turns out it's not a duplicate. Unduplicate done!