[Libreoffice-bugs] [Bug 51252] LO cannot start (reports runtime error with Visual C++ Runtime Library)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=51252

Stephan Bergmann <sbergman at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sbergman at redhat.com

--- Comment #28 from Stephan Bergmann <sbergman at redhat.com> 2012-07-25 09:15:49 PDT ---
There are a few things an affected user can do to help us track down the root
cause for this issue:

For one, providing a zip of LibreOffice's per-user configuration data
(typically located at something like "C:\Documents and
Settings\<username>\Application Data\LibreOffice\3\user") might help.  (It can
also help workaround this issue to move that directory away, see previous
comments.  LibreOffice will automatically re-create default configuration data
upon the next start, but for tracking down this issue, it would be necessary to
zip the original, failing data.)  That data should not normally contain any
really sensitive data, but you can always arrange to send the zip directly to a
trustworthy developer instead of attaching it here.  Alternatively, one
particular file within the per-user configuration data known to be notorious is
user\registrymodifications.xcu.  It might already help to only make available
that one file (and it might in turn already help to just move away that one
file to workaround this issue; again, it is automatically re-created with
default data upon the next start).

For another, one can install the Dependency Walker tool (depends.exe, see
<http://www.dependencywalker.com/>) and run LibreOffice from within it.  This
often gives useful information.  To do so, start depends.exe, load
program\soffice.exe from the LibreOffice installation into it ("File -
Open..."; depending on your Windows settings, the ".exe" extension might not
show, in which case there can be multiple files just named "soffice" in the
program directory; the soffice.exe one has the white LibreOffice document
icon).  Then "Profile - Start Profiling...", make sure "Automatically open and
profile child processes" is checked, then "OK".  This will start an additionl
window within Dependency Walker for the soffice.bin sub-process (which is the
one actually of interest to us), it is typically named all-caps "SOFFICE"
(whereas the original window for soffice.exe is named all-lowercase "soffice",
also see the "Window" menu).  Click through all the error messages indicating
that LibreOffice cannot start.  In that window for soffice.bin, the bottom
frame should give lots of output (leading up to some "Exited 'SOFFICE.BIN'
(process ...) with code ..."), copy all that output and make it available for
inspection.

For a third, the next LibreOffice 3.6.0.3 rc will hopefully show a somewhat
more detailed "Fatal Error" message box with some "Uncaught exception"
information when a user is hit by this issue.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.