Bug 82426

Summary:	Start Center will not load after crash, defaults to writer
Product:	LibreOffice	Reporter:	Luke <lukebenes>
Component:	LibreOffice	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED NOTABUG
Severity:	normal	CC:	jbfaure, jmadero.dev, momonasmon
Priority:	medium
Version:	4.4.0.0.alpha0+ Master
Hardware:	All
OS:	Linux (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description Luke 2014-08-10 18:43:06 UTC

Steps to reproduce:

1. Start with a fresh build of LO 4.4
2. Launch $ instdir/program/soffice
3. Crash LO with something like Bug 79620
4. Launch $ instdir/program/soffice

Expected Result:
Start Center will load

Actual Result:
Writer will launch. 


Also because there is no command line option to force the Start Center to load you can't easily open files if you have Ubuntu 14.4 because of Bug 81861

Comment 1 Maxim Monastirsky 2014-08-10 18:59:34 UTC

It depends on the OOO_DISABLE_RECOVERY environment variable. For a dev build it set to 1 in instdir/program/ooenv. In a release build you should see the recovery wizard instead.

Comment 2 Luke 2014-08-12 19:37:07 UTC

I tested instdir/program/ooenv with 
export OOO_DISABLE_RECOVERY=0
export OOO_DISABLE_RECOVERY=1
In both cases writer started instead of the Start Center.

Even if that variable worked, is this really the correct behavior?

Comment 3 Maxim Monastirsky 2014-08-12 21:26:32 UTC

(In reply to comment #2)
> In both cases writer started instead of the Start Center.
You should reset your profile between the tries.

Comment 4 Luke 2014-09-01 17:05:44 UTC

Steps:
1)$ rm ../user/registrymodifications.xcu  
2)$ export OOO_DISABLE_RECOVERY=0
3)$ ./soffice
4)Crash Calc 
Result:
Writer always opens with no recovery dialog.

If this is really the desired behavior then I guess this bug can be closed. But with Bug 81861 and no command line option to force the start center, it's not ideal for tester and others that work with multiple versions of LO simultaneously.

Comment 5 Luke 2014-09-01 17:36:14 UTC

We need an edit button for comments like github. 
2) $ nano ooenv -> export OOO_DISABLE_RECOVERY=0

Comment 6 Maxim Monastirsky 2014-09-01 19:59:51 UTC

(In reply to comment #4)
> 2)$ export OOO_DISABLE_RECOVERY=0
> 3)$ ./soffice
But soffice then calls ooenv which overrides your export! For step 3 you should run 'soffice.bin' instead (or simply edit ooenv).

> If this is really the desired behavior then I guess this bug can be closed.
The main point of this is to disable the recovery wizard, so it won't get in the way of devs while debugging crashes.

> it's not ideal for tester
Right, but it's ideal for devs. And it can be easily changed by editing ooenv. Also keep in mind that it defaults to OOO_DISABLE_RECOVERY=1 only if you build yourself from source. Any downloaded rpm/deb/whatever shouldn't have it (AFAIK).

Comment 7 Maxim Monastirsky 2014-09-01 20:22:44 UTC

(In reply to comment #6)
> But soffice then calls ooenv which overrides your export! For step 3 you
> should run 'soffice.bin' instead (or simply edit ooenv).
Sorry, didn't see comment 5. You right, it seems that LO checks only for the existence of this variable, regardless of its actual value. Try commenting this export completely.

Comment 8 Maxim Monastirsky 2014-09-01 20:28:45 UTC

And a quick search shows that indeed we don't check for the actual value: http://opengrok.libreoffice.org/xref/core/desktop/source/app/app.cxx#2340

Comment 9 Joel Madero 2014-10-23 01:54:29 UTC

Can this be closed as NOTABUG - after reading the comments it appears like that's the case

Comment 10 Maxim Monastirsky 2014-10-24 08:47:02 UTC

(In reply to Joel Madero from comment #9)
> Can this be closed as NOTABUG - after reading the comments it appears like
> that's the case
Yes, it doesn't visible to the end user anyway.