You are here

[Closed] LibreOffice Portable already running issues

10 posts / 0 new
Last post
shadowlmd
Offline
Last seen: 1 year 3 months ago
Joined: 2012-02-18 11:42
[Closed] LibreOffice Portable already running issues

There are still few quirks in LOP launcher. For example, if you reboot PC, next time LOP will not start saying it's already running. Same with PC crash, etc. It should check for running processes instead of relying exclusively on file based locks.

John T. Haller
John T. Haller's picture
Online
Last seen: 5 min 9 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
LO or LOP

LO *hates* to be crashed and uses file-based locks. No way around that.

LOP will check for a crash and offer to clean up.

What exactly are you seeing and what is showing you the error?

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

shadowlmd
Offline
Last seen: 1 year 3 months ago
Joined: 2012-02-18 11:42
I'm not speaking of LO

I'm not speaking of LO itself. I am speaking of LOP launcher (LibreOfficePortable.exe). You can see what I am seing if you kill LibreOfficePortable.exe wile swriter.exe is running, for example.

So, here's step by step.

1. Start LO writer portable.
2. Kill LibreOfficePortable.exe
3. Close LO writer portable.
4. Goto 1.

John T. Haller
John T. Haller's picture
Online
Last seen: 5 min 9 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
And?

If I kill em all (LOP.exe, so.exe, so.bin) and then restart: LOP starts up and says 'bad things happened, don't do that, start again'. You start it again and you get LO's recovery console. Exactly as designed. What's wrong with this?

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

shadowlmd
Offline
Last seen: 1 year 3 months ago
Joined: 2012-02-18 11:42
My bad. I did not know that

My bad. I did not know that message will dissapear next time I start LOP. I was killing lock files manually all the time. That's a bit confusing.

Anyway, when it couldn't start LO at all because of a bug, it was creating some lock file in Data, which wasn't cleaned up. Launcher was saying something like "LO is alrady starting" every time. In this case a check of file's age would solve the issue, i.e. if it's trying to start for more than a minute and there is no LibreOfficePortabe.exe process, something definetely went wrong and lock should be removed.

John T. Haller
John T. Haller's picture
Online
Last seen: 5 min 9 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Launcher Hang

That was a situation where the launcher itself was hung mid-startup, which has never happened with any app before, due to the fonts issue, which will be resolved with the .1 release. When you tried to run it again, it was already running (and hung) and would say so. It isn't something that can be resolved with lock files.

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

shadowlmd
Offline
Last seen: 1 year 3 months ago
Joined: 2012-02-18 11:42
No. When I tried it again, it

No. When I tried it again, it was NOT already running (and hung), because I killed process and even restarted PC. There was only one lock file left in Data directory and removing it would let LOP launcher run again. And it can easily be fixed by checking if the LibreOfficePortable.exe that created this file is still running.

John T. Haller
John T. Haller's picture
Online
Last seen: 5 min 9 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Mid-Startup

The launcher checks itself for running mid-startup via the file. I'll make a note for the PAL guys to check this out. As a crash mid-startup is normally exceedingly unlikely, I wouldn't classify this as critical, though.

IIRC, this is being fixed in PAL 2.2 or 3.0 already. Chris or kAlug will know for sure. I just emailed them to take a look at this to see if it is.

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

Chris Morgan
Chris Morgan's picture
Offline
Last seen: 7 years 5 months ago
Joined: 2007-04-15 21:08
"Fixed" in 2.2

This is indeed fixed in 2.2, so that the starting/stopping states are handled with mutexes and not saved to disk. Thus, if you try starting another instance while one is starting, it'll say "hang on, I'm busy" (just as Firefox does if you try running it while an existing instance of it is starting or quitting), but if you kill it while it's starting it'll go merrily on its way.

You should realise, however, that at that stage it will potentially corrupt data or lose settings; if you kill it while it's starting or stopping it's left in an indeterminate state at present. The only difference between 2.1 and 2.2 will be that 2.2 won't complain in that case.

In the mean time, if you get stuck in the starting/stopping state, delete Data\PortableApps.comLauncherRuntimeData-LibreOfficePortable.ini or remove the "Status=starting" line from it.

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

barky
Offline
Last seen: 4 weeks 3 hours ago
Joined: 2008-12-20 09:09
also getting issue

am unable to start 3.5.3, am getting following message:
another instance of LibreOffice Portable is starting. Please wait for it to start before launching it again

I can wipe the portable libreoffice, then reisntall & still get message ... even still get message after a reboot of my win7 x64 machine

I then revert to 3.5.2 and all works as it should, but 3.5.3 installed on a portable hard drive still fails ... seems final step of install, where you tick box to start libreoffice is failing somehow

EDIT: wiped it again & somehow it works now even without copying in the libreofficeportable exe to the folder ... hmmm

Log in or register to post comments