the last version and the current version of libre office does not run for me after update.
During the initial splash, crashes and it is not possible to start it again.
I have few extensions added, but it is only czech and swiss-german dict in fact, set fonts and so on, and nothing else.
There is simply no way to start it, I only can completely remove the folder, make new install and then make all setting again, as it even will not accept my old user profile.
any experince with that?
ADMIN ADDITION: This bug is being handled in this topic:
https://portableapps.com/node/31300
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
same situation here... crashed during splash....
I also having same problem.
DEP has closed LibreOffice Portable 3.5
vista business
have taken the previous version, blanc plain fresh install and the current version plain install and copied the settings folder to the new one, it does crash as well, so it seems to be one of the bundled extensions which is the culprit.
Otto Sykora
Basel, Switzerland
Can you trace it to a specific extension in your Data directory? Or even zip up your Data directory to I can troubleshoot it for you. My tests upgrading from LO Portable 3.4.5 to 3.5.0 seem to work fine with the one caveat that you often need to run it twice the first time after you upgrade (so it can finish upgrading settings it seems).
Sometimes, the impossible can become possible, if you're awesome!
will this do?
https://docs.google.com/open?id=0B0dtthBQTOpRNDI4NTdhMDEtOTEzYS00MmUwLWI...
I have zipped the data folder from the last version.
it should be here:
https://www.wuala.com/ottosykora/SHARED/DAT/?key=nCs62R33czrV
Otto Sykora
Basel, Switzerland
I have never installed any extensions and it crashed as well. I tried a completely new, clean install (not on top of the old previous version) - same thing. PC is Win7 Ultimate 64bit. It gives the "stopped working" error twice one after the other - once I close the first one it immediately displays the second one.
The first error's details are:
Problem Event Name: BEX
Application Name: soffice.bin
Application Version: 3.5.0.13
Application Timestamp: 4f2a576b
Fault Module Name: StackHash_4c4a
Fault Module Version: 0.0.0.0
Second error details:
Problem Event Name: APPCRASH
Application Name: soffice.bin
Application Version: 3.5.0.13
Application Timestamp: 4f2a576b
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.1638
What location are you installing to? Are you installing MultilingualNormal or MultilingualAll? Are you using the experimental Remove Additional Languages option?
I should note that I run both on my Win7 64-bit box without issue from P:\PortableApps\LibreOfficePortable.
Sometimes, the impossible can become possible, if you're awesome!
To solve the problem have to delete the old installation folder and install LibreOffice in a new folder.
I personally have in staled all on anusb stick, all in default position.
When updating, getting same error/crash.
Installing previous version into the same position, running first (no extra extensions etc) and then making the update to it causes the error/crash also , with same tex (BEX.. etc)
Only clean install does work.
I used multilingual normal , removal of extra languages not ticked.
w7 pro, x64, german
Otto Sykora
Basel, Switzerland
After trying all kinds of different combinations, my conclusion is that it won't run from my default Portable Apps location, which is: e:\Programs\PortableApps\LibreOfficePortable\
The installation itself is good as when I copy it into ANY other location it works.
The version I've been trying is LibreOfficePortable_3.5.0_MultilingualNormal.paf.exe - with and without the Remove Additional Languages option.
At first I thought it might be the length of the path, but I ruled this out as well. It has something to do with this particular folder - [PortableApps]. I tried comparing its properties to other folders, but couldn't see any differences.
Just to clarify, I did try installing and also copying LO to e:\Programs\SomeFolder and it works, so it's not the path itself. I also tried putting it into a much longer path, with more and longer folders and it still works. The only time it won't work is if I put into the [PortableApps] folder. I also tried installing it into a different folder and THEN copying it into [PortableApps] folder, and it once again won't work.
UPDATE: It also won't work from the [Documents] folder, or any folder inside it.
As far as I can recall the [PortableApps] and [Documents] folders were created by the PortableApps Menu awhile ago (StartPortableApps.exe dates back to May, 2008). I never really used PAM, so I never updated it - maybe that's the issue?
Any ideas, why these folders might be causing problems?
portableapps should be run from e:\ (or whatever you have) ... not inside any other folders
Although all of our apps should be able to be run from the root, they are originally intended to be run from X:\PortableApps\APPNAMEPortable
John,
I think some users are encountering slightly different start-up issues,but believe they are talking about the same thing, which may lead to some of the frustration I'm hearing, though they may indeed trace back to the same root problem. In another post, docda refers to receiving a false positive from McAfee Antivirus on attempting to download the paf file for LibreOffice v.3.5.0, flagging it as the Ransom-G.a trojan. I was able to download this file fine, but on trying to run the installation also received an identification regarding the Ransom-G.a trojan trojan, even though none of my other anti-virus apps saw anything threatening about it. It specifically referenced the file filterconfiglo.dll and deleted it. This is true whether I used the automated update or explicitly downloaded the LibreOfficePortable_3.5.0_MultilingualNormal.paf.exe file. If I later tried to launch LibreOffice it would try to launch and some of the initial screens would come up, but appeared to hang somewhere in the process. As an additional data point, it might be worth having everyone who is experiencing this start-up problem to go back and review the log of their anti-virus product, as it is sometimes easy to miss the notification, particularly on long installs, and they might have not realized an issue existed until they tried to launch the app. While I prefer my computer systems to work deterministicly, depending on why the false positive was generated, it might depend on what else was going on with the system at the time, so that they may get a later install to work, as other users have reported.
I'm currently trying to see what effect that rolling back to version 3.4.4 will have and will provide an update later. Meanwhile, I have posted a query in one of the McAfee groups. Performing a search of their site shows no recent postings regarding either LibreOffice or Ransom-G.a. If I receive any feedback from them, I'll post it here.
For those trying to identify a pattern to the problem, here are a few additional details:
Operating System: Windows XP SP3
Antivirus Product: McAfee VirusScan Enterprise Workstation Version number: 8.5.0.781
Virus Definitions Version: 6624.0000
No changes in add-ins were performed between the previous LibreOffice update and this one, and it had been working fine. If you can think of any additional info that might be helpful to you, just let me know.
Cheers (and good luck!),
John
Same problem here.
Installed previous version via PortableApps.com Platform and it worked perfectly. Today it automatically updated to 3.5.0 and crashes upon start. Any application of the package. Windows 7 32-bit.
PortableApps on 160gb sata usb drive over installed previous version no issue. First run only thin I had to do was allow a bin file through firewall.
“Be who you are and say what you feel because those who mind don't matter and those who matter don't mind.” Dr. Seuss
no issues for me either, components of LibO were quite slow to activate once it was installed & would be much slower on usb thumb drives I assume
tried it on an old 2gb thumbdrive, it installs but it doesn't get past 'enabling: solver for nonlinear programming' starting LibO from menu!
the drive, will try to replicate it on an old 1 gb I have
“Be who you are and say what you feel because those who mind don't matter and those who matter don't mind.” Dr. Seuss
finally works after downloading installer manually --- kept trying without wiping first (as an experiment) -- don't know if its relevant but seems there was still a part of LibO running from last failed attempt to start program from PA menu.
must add: no problems observed on newer faster thumb drives or portable hard drives.
problems returned after usb stick plugged into another pc --- crashes even on a fast corsair usb2.0/3.0 drive --- solution for now is copy over entire LibreOfficePortable folder from a portable hard drive to get beyond libreoffice splash screen
Could someone who has libo portable fail to run at all, even a clean install, please install libo locally and then delete the files in libreofficeportabe\app\libreoffice and copy in the ones from the local install?
Sometimes, the impossible can become possible, if you're awesome!
I moved C:\Users\username\tool\PortableApps\LibreOfficePortable to
C:\Users\username\PortableApps\LibreOfficePortable.
now it works. thank you.
After several crashes I moved "I:\portableapps.com\PortableApps\LibreOfficePortable" on my USB stick to "I:\\LibreOfficePortable", then I ran Calc which wrote many files (could be seen by process monitor of sysinternals) and moved directory back to original location. It works since then.
Is this going to be fixed? I tried ununstalling/reinstalling via PortableApps.com Platform, it still crashes.
No extensions here, clean install.
-----PER CRASH DIALOGUE-----
Problem signature:
Problem Event Name: BEX
Application Name: soffice.bin
Application Version: 3.5.0.13
Application Timestamp: 4f2a576b
Fault Module Name: StackHash_4c4a
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00000000
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 4c4a
Additional Information 2: 4c4ad7529a34983b6293625c48169922
Additional Information 3: 4c4a
Additional Information 4: 4c4ad7529a34983b6293625c48169922
-----AND-----
Problem signature:
Problem Event Name: APPCRASH
Application Name: soffice.bin
Application Version: 3.5.0.13
Application Timestamp: 4f2a576b
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.17725
Fault Module Timestamp: 4ec49b8f
Exception Code: c0000005
Exception Offset: 0002df85
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: e8ad
Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863
Additional Information 3: e8ad
Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863
-----PER EVENT VIEWER-----
Faulting application name: soffice.bin, version: 3.5.0.13, time stamp: 0x4f2a576b
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x7495c9f1
Faulting process id: 0x10e0
Faulting application start time: 0x01cceed49eff3fe1
Faulting application path: C:\Program Files (x86)\Windows NT\Portables32\LibreOfficePortable\App\libreoffice\program\soffice.bin
Faulting module path: unknown
-----OR------
Faulting application name: soffice.bin, version: 3.5.0.13, time stamp: 0x4f2a576b
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000005
Fault offset: 0x0002df85
Faulting process id: 0x1730
Faulting application start time: 0x01cceed4d0529ea6
Faulting application path: C:\Program Files (x86)\Windows NT\Portables32\LibreOfficePortable\App\libreoffice\program\soffice.bin
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
LibreOfficePortable_3.5.0_MultilingualNormal.paf.exe was extracted to the path detailed above (with that experimental feature unchecked).
Three processes remain resident post-crash and must be ended manually: LibreOfficePortable.exe *32, soffice.bin *32, soffice .exe *32.
v3.4.5 in another subfolder in the same path runs A-OK.
Good luck.
Does a local install of 3.5.0 work on the same machine? When the local version is installed, does the portable one start working?
Sometimes, the impossible can become possible, if you're awesome!
Within the context of this discussion, I don't know what you mean by a local install. I opened the paf file from a path on the only hard drive partition C: and let it extract to a path on the same partition. My purpose in posting up the error dumps from the splash crash and event viewer was simply because no one else did. Sorry but I am unable to participate in the jPortable strategy. Another FWIW: both 64 and 32 bit "Java SE 6 U31" (6.0.310.5) are installed on that system. Again, good luck.
Hope this might help.
My portableapps located on root of external HD (x:start.exe) and the apps are located in x:\portableapps\
Like others had crash/shutdown on startup problem after the LO auto update to 3.5.
After downloading LO PAF file and installing using PA menu, "install a new app" and choosing experimental own language option. I get a multiple warnings as LO starts up (and fails) about incorrect Java version (which was also an auto update).
After PAF install of Java (like LO above) , LO is upgraded and working.
EDIT - forgot to add running on Win7 64 ultimate
... if You've added additional extensions to LO Portable or if the new version comes with new extensions never installed before, LO will try to enable this extension at start.
If no JRE is active or the combination of used JRE, LO version an extension is incompatible the process for the extension check at startup could crash.
Try to update the JRE to the last version, this should solve the problem.
Paid for Software more or less?
What You need is OSS!
Since people keep reporting issues without bothering to followup on questions asked about said issues, please read this first if you have an issue. Do not report any new issues until you follow these steps:
1. Install the latest jPortable alongside LibreOffice Portable. So if LO is at X:\PortableApps\LibreOfficePortable, jPortable should be at X:\PortableApps\CommonFiles\Java. Once the latest LibreOffice and jPortable are installed. Does it work? If not, move on...
2. Install a local copy of LibreOffice (regular LibreOffice into Program Files, NOT LibreOffice Portable) and ensure it works on your machine. Then see if LibreOffice Portable runs. If it does, then uninstall LibreOffice. See if LibreOffice Portable still runs.
We need your assistance tracking down the issue. It does not appear to be a Visual C runtime issue with either version 8 or 9. But I do have one XP box where LibreOffice Portable will only run when LibreOffice is installed. I'm still trying to determine why. There were numerous changes in LibreOffice from 3.4.5 to 3.5.0. The installer changed and our build process needed updating. The directory structure and file locations changed, so we needed to update those as well. We may have missed something, though, so the more information we can get from everyone, the better.
Sometimes, the impossible can become possible, if you're awesome!
After seeing the confusion here, I thought I'd test and see if I could help....
For starters: LOPortable was updated through the platform (without error), platform is set to English, all tests were on 32-bit WinXP SP3.
On trying to run LOPortable I get the loading splash, which crashes out on the "Enabling: Danish spelling dictionary, hyphenation rules, and thesaurus" step.
Following your steps above:
1) I installed the latest jPortable. Same error, same place in the loading queue.
2) I then updated the local version of LO to 3.5.0. Tested to make sure it ran fine (it did), then ran LOPortable again. Once again I received the same errors as above.
3) I downloaded the LOPortable installer and updated manually (I did not select the option to remove unused languages). Once again the same errors.
4) I installed to a new directory to try a fresh install (once again, not removing unused languages). The fresh install worked as it should.
5) I removed the local copy of LO, and the new install of LOPortable still ran as expected.
6) I removed the Data\settings directory from my original, updated install. LOPortable then ran as it should.
I went through the Data/settings directory and started to swap out each directory/file for a copy from the fresh install until I could find the file in question, but, after swapping out either the entire Data/settings/user/config or Data/settings/user/config/soffice.cfg folders, the original install of LOPortable would always work fine, even after swapping back to the older version of the folder (this would possibly hint that is due to an issue with a different file, that was updated with a valid value when I swapped in the newer install's cofig or config/soffice.cfg folder and ran the program).
So it looks like a setting/file from the previous version is not compatible with 3.5.0. Potentially if there is more more than one file/setting at fault here, it might explain some of the differences people seem to be experiencing.
Nope. I have clean install through PortableApps.com Platform (which means there was no LibreOfficePortable directory at all on my drive) and it still crashes. So it looks like the problem is with default settings that come with the installation.
But a fresh install works perfectly for me, so maybe we have multiple issues going on.
Are you doing fresh install via PortableApps.com Platform, or you just download installation and run it directly?
I downloaded the installer manually for my earlier testing. Didn't think to move my existing install and try it from the platform, although honestly there shouldn't be a difference which way it is installed.
I've just installed LOPortable via the platform on my home PC (32-bit Win7) and it worked fine, though.
There are two separate issues afoot. One is an issue with certain profiles being upgraded. Another is an incompatibility between LibreOffice Portable 3.5.0 and certain PCs. Some people seem to be running into both.
Sometimes, the impossible can become possible, if you're awesome!
I guess you are right. I just deleted settings/user directory and it still crashes. Does official distribution install/update some system libraries?
I can confirm this one. The easiest method to get it up an running again is:
- Move your original LibreOfficePortable to a secure place as a backup (same drive is the fastest, but rename the folder afterwards to ensure it will not be overwritten).
- Install the latest 3.5 version to the same location where your original version first was.
- Delete everything in PortableApps\LibreOfficePortable\Data\settings\user of the new installation except for the folder 'config'.
- Copy the same contents from your backup to the mentioned folder except for the folder 'config'.
- Start LibreOffice from the PortableApps menu. It will configure itself and quit respectively.
- Delete the folder 'config' in PortableApps\LibreOfficePortable\Data\settings\user of the new installation.
- Copy the same folder from your backup to this place.
Up and running! I don't have any clue why LO 3.5 does not crash after this scheme (I have tried the same thing as @winterblood by using trial and error before I stumbled on this thread).
The only thing that seems being changed is the file 'fontnames.dat' according to its date. In the years some internal fonts have been renamed with their filenames containing underscores instead of hyphens. So if someone has any idea, please don't hesitate.
I can confirm this doesn't work for me. See above note.
when I a) moved the directory from "I:\portableapps.com\PortableApps\LibreOfficePortable" to "I:\portableapps.com\LibreOfficePortable" or b) when PortableApps has be renamed either to "PA" oder "Portable". It still failed when renaming it to "PortableApps_", "PortableApp_" or "Portable_".
The first successfull start it takes about 7 minutes until the LibreOffice main windows appears. During that period LibreOffice does a lot of configuration stuff, e.g.
"I:\portableapps.com\LibreOfficePortable\Data\settings\user\extensions\bundled\registry\com.sun.star.comp.deployment.help.PackageRegistryBackend\lua7jx6.tmp\es\help.idxl\segments_1".
When I a) moved it back to the original location or b) renamed it to PortableApps again then LO continues to work, even when started within portableapps launcher.
So it seems to be an issue of the pathname?
I tried it several times (on very same USB stick), uninstalled LO, reinstalled it, got the crash and did the different moves and directory renames and it always work after the first successful launch.
HTH.
PS: just saw the notes below regarding pathname and length. So it seems to be just an issue during the first run and longest pathname possible seems to be I:\portableapps.com\Portable\LibreOfficePortable"
Hello
for me it does not matter how and where do I install libreoffice 3.5 - I believe that the path is too deep (> 256 characters)
The longest path recommended is X:\PortableApps\LibreOfficePortable. Anything longer than that may not work and is not recommended. Your Desktop and My Documents folders are actually much longer than this.
Sometimes, the impossible can become possible, if you're awesome!
I had PortableApps.com Platform installed into D:\tools folder (D:\tools\PortableApps). When I moved it to a root of my drive (D:\PortableApps), LibreOffice launched without crash. I did not even reinstall it, just moved whole PortableApps directory. Full path to LibreOffice is D:\PortableApps\PortableApps\LibreOfficePortable. Why was it crashing while launched from D:\tools\PortableApps\PortableApps\LibreOfficePortable is a mystery to me.
Also, now I moved it back to D:\tools and it still works.
Anything longer than x:\portableapps\libreoffice can easily hit the file length limit and is unsupported. It can affect every run or just a first run or first after upgrade run. No idea why you have portableapps twice in that path of yours.
Sometimes, the impossible can become possible, if you're awesome!
Path soft limit is 256 characters on Windows. Hard limit is 4096 characters, IIRC. How can I hit even soft limit with a base path of 54 characters long? Seriously. The problem is somewhere else.
I just checked, longest path in LibreOfficePortable directory is 208 characters, it's D:\tools\PortableApps\PortableApps\LibreOfficePortable\App\DefaultData\settings\user\extensions\bundled\registry\com.sun.star.comp.deployment.configuration.PackageRegistryBackend\lu2agx6z.tmp\dictionaries.xcu
Regarding the double PortableApps in my path, it's easy, D:\tools\PortableApps is an installation path of PortableApps.com Platform. There I have Autorun.inf and Start.exe files along with Documents and PortableApps hidden directories. All apps are installed inside PortableApps hidden directory automatically via "Get More Apps..." menu item.
While LibreOffice is doing some things internally, it creates even longer paths (as you discovered when yours failed in your 54 character path). It does this on first run. On upgrades. And when using some extensions. So, again, anything longer than X:\PortableApps\LibreOfficePortable is unsupported and likely to cause issues.
Sometimes, the impossible can become possible, if you're awesome!
I guess PortableApps.com Platform should warn user about it then. When I installed it in D:\tools\PortableApps, I did not receive any warnings about unsupported configuration and possible application crashes.
It's not a platform issue. It's an issue with LibreOffice itself. Something we have zero control over. We'll likely pick an arbitrary safe number at some point with it and simply refuse installations into long paths to avoid issues like this coming up. Oddly, every time it causes an issue and is reported to us, it results in someone arguing that the path isn't the problem, or shouldn't be, or is something we did to break it. Despite the fact that it is an issue with the app itself and goes back to the very first versions of OpenOffice.org (see note). We used to have the launcher check for this issue before we switched it to PAL, but it was never 100% accurate in determining exactly what is 'safe'. And, of course, longer paths the install would just completely fail on systems with a 256 character limit.
Future versions of the PA.c Platform installer will encourage installation to the root directory of your drive but let you pick a custom path with a warning about potential issues like this.
Sometimes, the impossible can become possible, if you're awesome!
I did not try to say it was something you broke up. I just did not like the "anything longer than X:\PortableApps\LibreOfficePortable is unsupported" part which was a total surprise to me because Platform installer did not say anything about it. Now that you explained that issue was with LibreOffice itself and "not supported" was related to LibreOffice as well, it's all clear. I moved my installation to D:\apps as the shortest meaningfull path possible in my configuration, hope that will be fine.
254/255/260 characters is the operating system limit for normal paths; the file system can indeed cope with longer.
I have heard it suggested that LibreOffice creates (or works with) some longer paths still while starting; I don't know, as I have never tried pinpointing it. Another idea which has seems more probable has just occurred to me: it could be having redundant relative paths, e.g. X:\foo\bar\..\baz instead of X:\foo\baz. Thus it could easily run over. The main thing that I know of it is that it starts failing somewhere around 200 characters rather than around 250.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
I updated over an existing 3.4.5 version. Wouldn’t run.
Then a fresh install at c:\portableApps\LibreOfficePortable. Wouldn’t run.
Installed on a second computer at c:\portableApps\LibreOfficePortable. Ran OK.
Copied this to a flash drive at x:\portableApps\LibreOfficePortable. Ran OK.
Took that flash drive back to the first computer. Wouldn’t run.
Back-n-forth several times, same flash-drive, same story. Runs on #2, dead on #1.
Unremarkable old computers. #1 is XP Pro SP2, #2 is XP Pro SP3.
Obviously you should at least update your XP to SP3 before trying to run modern software on it.
Seems a lot of the systems I plug my drives in are seldom (if ever) updated. If that’s the new requirement I’ll have to step back to an earlier version.
I checked LibreOffice system requirements page and it does not list SP3. So, either they forgot to update the page, or the problem is somewhere else. I don't have pre-SP3 XP system anywhere so I can't really test this.
I can report same problem on English install. No extensions at all. After upgrade LO 3.5 "stopped working" during splash screen (Windows 7 64-bit). Reinstalled directly from portableapps.com, ie. didn't use portableapps launcher update feature. Still crashes during splash screen. Deleted LO folder in portable apps folder and did a clean install. Same result, so it seems to be something in the installation. Installed on three PCs - all exhibit same effect.
Try this:
1. Install PortableApps.com Platform into root of the drive, or into a short named directory like C:\Apps.
2. Install LibreOffice via Platform (Get More Apps... menu item)
I'm sure it will work.
Don't install the platform to X:\Apps, install it directly to X:\
Installing the platform to anything but the root of the drive ensures that the path is too long, internally, for LibreOffice, as previously indicated.
Yeah, 4 characters longer is "too long". As previously indicated, LibreOffice works fine even if Platform is installed in X:\PortableApps, which is 8 characters longer than X:\Apps. Installing something into a root of the drive is not always an option and in general a very bad idea, unless it's a USB stick entirely dedicated to PortableApps.
that these are supposed to be installed on usb devices and their ilk. And there is a difference between installing on the root and installing on any other location besides the 4 characters.
Don't be an uberPr∅. They are stinky.
I guess portableapps.com website is wrong then, stating something like "Portable software for USB, portable and cloud drives".
And yes, there is difference besides 4 characters. When installed into a root of a removeable drive, inserting the drive will autorun the Platorm. That's the only difference.
The platform can be installed to any of those, and is by millions of users; however, we recommend installing the platform to the root directory only, for cases like this. That does not mean that you cannot install it elsewhere, just that if you do, it's an unsupported setup.
[EDIT] And no, inserting a removable drive into any up-to-date Windows system will NOT auto-start the platform, as auto-starting from removable media has been disabled by Microsoft.
Unsupported setup? Seriously, by default appliactions store their settings in %APPDATA%\ApplicationName, which expands to C:\Documents and Settings\Username\Application Data\ApplicationName on Windows XP. In case of LibreOffice, this path would be at least 63 characters long (assuming user account is "Username" which can be much longer). In PortableApps.com Platform (assuming it's installed in X:\Apps) LibreOffice's appdata would be in D:\apps\PortableApps\LibreOfficePortable\Data\settings, which is 54 characters, which is at least 9 characters shorter than default path on Windows XP. How can this be an unsupported setup?
Yes, it just brings up a dialog allowing to choose either to run something specified in autorun.inf or show contents, or do nothing.
It's unsupported in the sense that your Autorun.inf will not function properly, and the PortableApps.com Installer will not be able to auto-select a path for you. Use [X]:\Apps if you want, but be aware that there may be upcomming features that rely on having your platform in the root drive.
This discussion is over. It's getting far too aggressive, and leading us from the original topic.
Sorry for agressiveness. My point is and will be that if something is allowed by installer, it should not be unsupported. I did not use any hacks to install platform in a subdirectory.
Going back to the topic, LibreOffice works fine when Platform is installed in X:\Apps and it's not just a luck, but a simple comparation of path lengths proves that it's absolutely fine.
In my opinion, if there going to be any features, affecting application functinality, that rely on Platform being installed into a root of the drive, there should be a solid warning upon update and an option to move installation to a root drive automatically. Or at least don't update until installation is moved.
PS: Sorry if it looks agressive, my english is not perfect and it's hard to make a point and being nice at the same time. Always been a problem for me.
My point is your point doesn't matter in this thread. We are attempting to fix an unrelated bug. So path length is unrelated. Let it go.
Sometimes, the impossible can become possible, if you're awesome!
We get that you really want to use a subdirectory. This entire bit of the thread is now offtopic and getting in the way of the real work of fixing the bugs in LO Portable. No more bickering about this to all involved.
Sometimes, the impossible can become possible, if you're awesome!
Well, ideally, I should be able to install it where I need it. But I understand that some programs (and LibreOffice is not the only one) don't like being in subfolders or too many directories deep.
Anyway, I found a workaround that worked for me. My normal path is C:\Users\Chris\Portable Apps Launcher\PortableApps\LibreOfficePortable. It was from this location that the upgrade to 3.5 failed to run (despite my initial install of 3.4 in that location working fine. So, considering some of the advice above, I copied the "broken" installation's LibreOfficePortable folder to the root directory of C: and ran it from there. It initialized and opened. I then shut it down and copied the folder back to it's original location, overwriting the original installation and ran it. It ran perfectly.
Further experimentation running from a network location at various paths:
S:\Dataserver(\\LS-CHL9A2)(S:)\LibreOfficePortable WORKS;
S:\Dataserver(\\LS-CHL9A2)(S:)\Portable Apps Launcher\ LibreOfficePortable WORKS;
S:\Dataserver(\\LS-CHL9A2)(S:)\Portable Apps Launcher\PortableApps\LibreOfficePortable WORKS;
The last path is my backup location for my portable app library and version 3.4 ran from there no problem. Version 3.5 only worked after implementing the workaround.
So I don't know if the assessment that the path length is the problem is correct since after running the app at a admittedly shorter path length to initialize it, it runs fine from the longer path length locations. And, I do want to point out that OpenOfficePortable runs from any of the above locations without any issues, as well with the last update from the Platform updater, without any of these workarounds.
Anyway, certainly a curious anomaly, but not more than a minor inconvenience at most, considering the benefits gained by running portable apps, and particularly the Portable Apps Platform. With luck, they'll have it worked out for the next update; if not, it's certainly easier to fix than a full install version of any program!
Cheers!
Nice dude, I use this solution for my looooooong path(like X:\Documents\Programs-P\PortableApps_MainFolder\PortableApps\LibreOfficePortable), of usual PA installations...and LibreOffice 3.5 now run like all other applications on my PC's. Tnx a lot
Why not just run from a partition? ..... simplifies things a lot I find ... then copy & paste big programs over to wherever
Organization? Free mode to use own PC's? It's so difficult to understand? If so many users had experimented problems there's a problem inside installer. A guy has found the solution? I say many tnx to him because he solved this situation...and we all waiting for next version(unbugged we hope). Easy and easy, for users is the better way.
This problem is inside PA pakage? Ask to they.
This problem is inside LO developers pakage? Ask to they.
You can't ask users to change own PC's organization for just one application....this is a joke.
You can when it's technically impossible for one app to actually run from said path due to its internal structure. Users with these overly long paths have a choice between switching to a recommended and supported path like X:\PortableApps\LibreOffice or not using the app. It's up to the user, but that's the choice. And those are the only options. As we've said, the issue is due to the way LibreOffice is structured internally. Which is a holdover from OpenOffice.org. It's been an issue for, literally, years. And is unlikely to change.
Sometimes, the impossible can become possible, if you're awesome!
I struggled as well but found if jportable (&jportable launcher just to make sure)were installed with java enabled in libreoffice 3.4.5 & then 3.5.0 was installed on top it worked fine on a flash drive ..... I remember now that old versions of openoffice.org had similar requirement for java to be enabled when jumping to new version.
Since multiple people didn't respect the "please stop re-reporting" request above and many others went offtopic arguing about unrelated issues, I have created an actual bug report thread over here:
https://portableapps.com/node/31300
All actual bug stomping will take place in that thread.
Sometimes, the impossible can become possible, if you're awesome!
I'd like to make a few more observations re: path length.
My views on running PA from a subdirectory are well-known. I also had issues with 3.5's initial startup in my normal location, so I moved it to C:\PortableApps and it started up after several minutes - then I moved it back to my normal location and it worked.
This got me thinking about the whole path length issue, which has been an ongoing thing since OOo days. It's problematic for a developer to configure an app to run close to the file path limit, especially an app that encourages 3rd party plug-ins. This is, at its heart, an issue that LO needs to address*. At present, it appears that a normal (non-portable) install of LO has given itself enough space to function without crashing.
Comparing the path length to soffice.exe between my normal install and a standard PA.c install:
C:\Program Files (x86)\LibreOffice 3.5\program
vs
X:\PortableApps\LibreOfficePortable\App\libreoffice\program
shows that the standard file structure of PortableApps adds several folders and 14 more characters (I'm counting spaces in my normal install path).
This makes me concerned that the PortableApps version will always be more susceptible to file path issues that do not show up in a normal install.
*Therefore, while this is an issue that LO should address, it is less critical to them than to PortableApps.
I made this half-pony, half-monkey monster to please you.
It's not critical. It's a want not a need. There's no need to have really long paths you keep your apps in. Most users use PortableApps.com off the root as intended. The upcoming platform installer won't even give the user a chance to install to a custom path by default (unless they click on an 'advanced' option and then they get a warning). Installing to oddball locations makes it harder to get at your apps and means app installers and plugin installers won't find the platform when run. LibreOffice Portable will work for the OCD types that really want their Start.exe, Documents and PortableApps folders inside something else in the root like PortableApps or Portables. It won't work for the uber-OCD who want it in Tools\Software\Portables\PortableApps.com. None of this is a mission-critical issue. It will likely never be fixed by LibreOffice or OpenOffice.org. So, honestly, it's completely moot to discuss. If there were an easy fix, I'd happily do it. But there isn't. And we can't.
Again, this is off topic in this thread and it's just covering the exact same ground people have covered for years, adding nothing to the conversation and adding nothing to the solution.
Once again, please refrain from off topic posts in this thread. We have work to do here.
Sometimes, the impossible can become possible, if you're awesome!
In the future, I will start a new thread if I feel the need to discuss this. Good luck on your bug hunt.
I made this half-pony, half-monkey monster to please you.
Once again Libre Office fails to run after update this time the version is 3.5.5. Stops at splashscreen. The problem this time is that same as last time. The office file is too deep in a directory, this is strange because it worked in same place before upgrade. However taking file to top level of directory, it works again. Don't know why but this solves it. Win7 64 bit. So if your is not working, maybe this will solve it for you too.
Try resetting it by removing the Data directory.
Sometimes, the impossible can become possible, if you're awesome!
I had the same problem with LibOP upgrade to 3.5.4. (reported in https://portableapps.com/node/32962). In my case it's surely no matter of pathlength (all standard). Renaming X:\PortableApps\LibreOfficePortable\Data\ helped (John T. Haller speaks of deleting here).
Just an additional suggestion: Try deleting only X:\PortableApps\LibreOfficePortable\Data\settings\user\extensions first and/or backup other parts of the Data-directory if you don't like to lose all settings including your templates.
In my case first launch after measures took long time and did not result in a running instance. Second launch was finally successful. Since then no issues - even not with upgrade to 3.5.5 .