You are here

[Fixed] LibreOffice Portable 3.5.3.1 doesn't delete registry.dll upon exit

10 posts / 0 new
Last post
Double Impact
Offline
Last seen: 8 years 6 months ago
Joined: 2011-11-19 03:33
[Fixed] LibreOffice Portable 3.5.3.1 doesn't delete registry.dll upon exit

The new launcher unfortunately leaves folders ns*.tmp with registry.dll
when it completely closes.
This happens with the 3.5.3.1, which I've downloaded from
https://portableapps.com/apps/office/libreoffice_portable
just today.
Hope this helps to find the source of the problem:
1) This behavior is also present in LibreOfficePortable.exe launcher fix 2
2) This doesn't exist in the patched LibreOfficePortable.exe launcher
from May 11, 2012 -
https://portableapps.com/downloads/app_extras/libreoffice/no_vcr_check/L...

Another question - is it possible to turn off the splash screen with progress bar?

barky
Offline
Last seen: 3 weeks 2 days ago
Joined: 2008-12-20 09:09
I seem to have 3.5.3.2

perhaps a fix was in that?

Double Impact
Offline
Last seen: 8 years 6 months ago
Joined: 2011-11-19 03:33
Re: I seem to have 3.5.3.2

As far as I know, there's no such official version released.
The latest is 3.5.3.1 Smile

Bindlestiff
Offline
Last seen: 1 day 11 hours ago
Joined: 2009-11-10 22:42
I also seem to have 3.5.3.2.

I also seem to have 3.5.3.2. Clicking on "about" in Calc shows:
LibreOffice 3.5.3.2

Double Impact
Offline
Last seen: 8 years 6 months ago
Joined: 2011-11-19 03:33
Re: I also seem to have 3.5.3.2.

Yeah, the program "Help - About" says 3.5.3.2 for me also.
I was talking about the version that resides in appinfo.ini
PackageVersion=3.5.3.1
DisplayVersion=3.5.3.1
Program version info and PAF version don't have always to be totally identical.
3.5.3.1 means more like 3.5.3 Rev 1 here (I believe so)

Bindlestiff
Offline
Last seen: 1 day 11 hours ago
Joined: 2009-11-10 22:42
I checked a different

I checked a different installation where "Help - About" says 3.5.3.2.
appinfolini says:
PackageVersion=3.5.3.0
DisplayVersion=3.5.3

Oh well ... as long as it works ...

John T. Haller
John T. Haller's picture
Online
Last seen: 54 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Fix: Edit LibreOfficePortable.ini

To fix this for now, just browse to App\AppInfo\Launcher and open up LibreOfficePortable.ini. The 8th line down says XML=true. Hit enter at the end of that line to create a new one and have it read:

Registry=true

Then save it.

Sometimes, the impossible can become possible, if you're awesome!

Double Impact
Offline
Last seen: 8 years 6 months ago
Joined: 2011-11-19 03:33
Re: Fix: Edit LibreOfficePortable.ini

John, good day to you! Thanks for the quick response and for the fix.
It works as it should now.

The odd thing is that the bug I've described doesn't even appear on my
main work computer running Windows 7 32-bit.
This happens only on my home computer which has 64-bit Windows 7 on it.
Can't understand the connection between these facts - because both
computers do not have LibreOffice installed locally on them.

Btw, is there any way to toggle splash screen on/off?
I mean the one with the progress bar right after starting the launcher.

John T. Haller
John T. Haller's picture
Online
Last seen: 54 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Registry

It's based on whether it uses the registry. On machines with a standard installed VC runtime, the launcher finds it without the registry. As a fallback, it checks registry keys for non-standard installs so it doesn't bug you to install a runtime that is already there. So, your home computer has a VC runtime but it isn't responding to standard detection, but is found via its uninstall keys. Doesn't mean anything is wrong, VC runtime detection is kinda flakey.

The splash is LibreOffice's splash not ours, so you need to disable it in the options.

Sometimes, the impossible can become possible, if you're awesome!

John T. Haller
John T. Haller's picture
Online
Last seen: 54 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Fixed in 3.5.4

This is fixed in 3.5.4 with the launcher correctly cleaning up the registry dll.

Sometimes, the impossible can become possible, if you're awesome!

Log in or register to post comments