1. Install LibO, I use Administrative install (msiexec /a)
2. Do anything to make sure that this installation will create new user profile, such as:
2A. After install finished, go to path-to-installation/program/bootstrap.ini, change the value of UserInstallation to UserInstallation=$ORIGIN, or
2B. Delete old user profile
3. Run path-to-installation/program/soffice.exe
Actual: Splash screen show, and LibO closed. The process soffice.bin/.exe are not found in Task Manager. I have to run soffice.exe again to open LibO
Expected: Splash screen show, and LibO open at Start Center
4. After LibO open at start center, close it by File > Exit.
5. Delete user profile
6. Run path-to-installation/program/soffice.exe, the result is same as the above.
7. Repeat step 4-6, the result is still the same
So, I conclude that, after creating user profile, LibO close, no matter it's the first run after install or not.
[REPRODUCIBLE] on Administrative install on Windows XP, with:
pull time 2012-05-18 00:57:37
git core: 3da4ab93e14bbe472ac0a6bce52616a93a2506d2
(In reply to comment #0)
> [REPRODUCIBLE] on Administrative install on Windows XP
Also REPRODUCIBLE with normal install of same build (by double-click the installer, and following the wizard) on Windows XP.
with Administrative install (msiexec /a), still [REPRODUCIBLE] on WinXP with
> tinderbox: W2008R2@16-minimal_build
> pull time: 2012-05-28 04:23:11
> core: b5f066e64a49aa007e04dc57dc0bbd0857ca0e2f
Some testing indicate that this problem is regression BETWEEN
> tinderbox: pull time 2012-05-02 06:53:41
> tinderbox: pull time 2012-05-06 22:03:33
I didn't download any tinderbox builds between May 02 and May 06
Reproducible on WinXP 32b
pull time 2012-05-28 04:23:57
That happened with each of the pre-installed extensions (other pre-installed extensions each time removed).
Rename the folder 'extensions' [path-to-installation\share\extensions] to 'extensions_bak' (or remove all extensions from folder 'extensions'; then LibO will not be closed.
It is normal that soffice.bin exits early (with a special exit code of 81) whenever it detects that the bundled and/or shared extensions are not in sync with the corresponding user profile data (which is esp. the case when a new user profile directory is created). However, the outer soffice.exe should restart soffice.bin when it exits with the special code of 81. Would be strange if that mechanism stopped working.
I guess that this is duplicate of the bug 43989.
[REPRODUCIBLE] on Windows XP with build from tinderbox Win-x86@6-fast, pull time 2012-06-05 10:06:05, core: 4cf7551c24f5dad694fecbb2b80b2b52173ffdb7
[NOT REPRODUCIBLE] on Windows XP with build from tinderbox Win-x86@6-fast, pull time 2012-06-05 23:16:58, core: b255de87082d11a42d7af7860dcc4e971342df06
So, I think yes, the fix also help here. Thanks Andras! :-)
*** This bug has been marked as a duplicate of bug 43989 ***
(In reply to comment #4)
> It is normal that soffice.bin exits early (with a special exit code of 81)
> whenever it detects that the bundled and/or shared extensions are not in sync
> with the corresponding user profile data (which is esp. the case when a new
> user profile directory is created). However, the outer soffice.exe should
> restart soffice.bin when it exits with the special code of 81. Would be
> strange if that mechanism stopped working.
I think that this is the case (started from LibreOffice 3.4). The fix of bug #43989 only prevents this happening, so we need to investigate a little bit, why this mechanism stopped working.
(In reply to comment #7)
> The fix of bug
> #43989 only prevents this happening, so we need to investigate a little bit,
> why this mechanism stopped working.