Bug 51084 - soffice.exe closes without displaying the application chooser if there are no LibO settings in the user profile
Summary: soffice.exe closes without displaying the application chooser if there are no...
Status: RESOLVED DUPLICATE of bug 43989
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
3.4.5 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2012-06-14 09:11 UTC by rpr
Modified: 2012-06-14 13:27 UTC (History)
0 users

See Also:
Crash report or crash signature:

screenshot of performance of soffice.bin in Process Explorer (8.91 KB, image/png)
2012-06-14 09:11 UTC, rpr

Note You need to log in before you can comment on or make changes to this bug.
Description rpr 2012-06-14 09:11:45 UTC
Created attachment 63035 [details]
screenshot of performance of soffice.bin in Process Explorer

How to reproduce:

On a MS Windows 7 Pro. SP1 32-bit (tested on a PC with AMD Athlon II
X2 CPU on 3 GHz with 2 GiB of RAM) make a clean install of LibreOffice using LibO_3.5.4_Win_x86_install_multi.msi. All additional
components were selected but no additional user interface languages
except English. Java 6 Update 32 was previously installed in Windows.

There are no LibO settings in the user profile, i.e.
"%APPDATA%\LibreOffice" directory does not exist (substitute %APPDATA%
with the value of the environment variable for the current user, e.g.
C:\Users\Administrator\AppData\Roaming\). You can test this on a user
account which has not used LibO previously or simply delete the
existing "%APPDATA%\LibreOffice" directory.

The user starts the soffice.exe for the first time which then runs for
some time and then closes without offering the LibO application
chooser. I'd say this may be confusing/frustrating for users,
especially if they are new to LibO.

During the execution of soffice.exe LibO settings have been created in
the "%APPDATA%\LibreOffice" directory. No messages related to LibO
have been logged in the Event Log.

Subsequently soffice.exe starts quickly and shows the application

I monitored the execution with Process Explorer and Process Monitor
(see http://technet.microsoft.com/en-us/sysinternals) and saw the
following: soffice.exe started soffice.bin which was then quite busy
for 150 seconds (see the attached performance graph) but eventually
closed. If someone would like to analize the execution, here is a link
to the zipped log (30 MiB) which can be opened in Process Monitor:
Comment 1 Andras Timar 2012-06-14 13:27:37 UTC

*** This bug has been marked as a duplicate of bug 43989 ***