Some people are experiencing issues with LibreOffice Portable 3.5.0. This topic is to discuss and nail down the bugs behind a couple of those issues. Some background details on some of the issues are in this thread.
1. Path too long. On some PCs with some installs, too long a path can lead to issues. This is NOT something we are addressing in this thread, regardless of your opinion of whether it should or should not be an issue or should or should not be warned about by the installer or platform. If you have LibreOffice Portable installed to a long path, please do not participate in this thread. We're worrying about other bugs and anything related to oddball paths working or not is a distraction.
Fix: Just install to a shorter path. X:\PortableApps\LibreOfficePortable is the recommended path.
2. McAfee being dumb. McAfee went off and decided that a couple random files in LibreOffice Portable were infected and deleted them without asking whether you wanted to. This is a false positive on the part of McAfee and you will be unable to use LibreOffice Portable (and possibly LibreOffice as well) until they fix their broken definitions. If you are experiencing this issue, please do not participate in this thread. We can't do anything on our end to fix McAfee's bugs.
3. Upgrade issues. Upgrading some working installs of LibreOffice Portable 3.4.5 to 3.5.0 causes it to stop working. However a clean install on the same machine works fine. This is one of the issues we are discussing but you have to be sure that a clean install is working and the upgrade is not to ensure this is your issue. This issue seems to manifest as LibreOffice freezing part way through starting up.
4. Outright failure. On some PCs, LibreOffice Portable 3.5.0 fails to work at all. Even thought it is a clean install into a supported path like X:\PortableApps\LibreOfficePortable. A quantified version of #4 is the error "Fatal Error - The application cannot be started. an error occurred during file opening". We can reproduce this reliably on a clean, fully patched Windows XP SP3 test machine and are working on a fix. Note that installing LibreOffice locally allows it to work. Uninstall and it starts failing again. So it is something else being registered by LibreOffice 3.5's new MSI installer.
Temporary Fix: As a temporary workaround, install the current Microsoft Visual C++ 2008 Runtime on the local machine to alleviate the issue. A permanent solution within the portable package itself is being worked on.
Please do not re-report any information that is already contained here.
I can only confirm, that fresh install of 3.5.0 works where ever it is located, but upgrade from 3.4.5 does not.
No local LO or OO or SO installed on any machines. Tried on w7 starter, w7 pro, XP sp3.
Installation on default position on usb stick, latest java on stick and PC in default position.
Otto Sykora
Basel, Switzerland
I just installed PortableApp LibreOffice and it would not run but then found a simple odd fix. I never used LibreOffice before, a fresh install. I put it on a Seagate external hard drive plugged into a Dell Inspiron laptop with Windows 7 and the path is
T:\PortableApps\LibreOfficePortable
During first use, Windows says "LibreOffice 3.5 has stopped working" and offers a "close program" button. For the first install I chose the experimental language removal. So I uninstalled and reinstalled normally, with nothing experimental. It did the same on launch, it would get up to the loading description "Enabling: English spelling dictionaries, hyphenation rules, thesaurus, and grammar checker" then quit. During writing of this, while getting the path to the app I clicked the app icon directly in Explorer, not in the PortableApp Platform. Suddenly it ran like it should. After that, it ran from the Platform Launcher interface. Maybe the problem is primarily my setup, I don't know, but I saw others with issues and thought I'd try to help. Writing this helped me, great app.
thank you~
Running LibreOffice 3.5.2 may result in an error on some Windows XP machines. As a temporary workaround, install the current Microsoft Visual C++ 2008 Runtime on the local machine to alleviate the issue. A permanent solution within the portable package itself is being worked on.
Sometimes, the impossible can become possible, if you're awesome!
The above issues are fixed in LibreOffice Portable 3.5.3. It can detect when a local machine is out of date in terms of runtimes that would interfere. And the path issues are fixed.
Any new issues with newer releases, please create a new ticket. Thanks!
Sometimes, the impossible can become possible, if you're awesome!
I see that LibreOffice Portable 3.5.3 offers to install the missing MS Visual C++ runtimes when the application is starting. It appears to be an each-time deal, as when I close LibreOffice and restart the same offer reappears.
Is there a more permanent portable solution planned, whereby when once the fact the runtimes are missing is detected and the offer to install them is made and accepted, they then stay installed so that the routine does not need to get continually repeated?
I can confirm this bug. I have a write-up of it here: https://portableapps.com/node/32157
There's also a patched launcher you can grab for now that will disable the message for you.
Sometimes, the impossible can become possible, if you're awesome!