Bug#540428: openoffice.org-common: soffice -no-oosplash throws RuntimeException
Package: openoffice.org-common
Version: 1:3.1.0-5
Severity: important
Since upgrading to 1:3.1.0-5 in testing, invoking soffice with -no-oosplash
results in a runtime exception before any windows are displayed:
windlord:~> soffice -no-oosplash -writer ./FY10-SGG-Authentication.doc
terminate called after throwing an instance of 'com::sun::star::uno::RuntimeExce
ption'
If I remove the -no-oosplash command-line option, everything works exactly
as expected. However, since the default .mailcap entries include
-no-oosplash, this requires a bit of reconfiguration.
I've tested that this also happens with -calc instead of -writer, so it
appears to be something in the wrapper rather than in the separate
applications.
I've deleted my .openoffice.org and .openoffice.org2 directories and let
OpenOffice recreate them, without any effect on this problem.
I'm fairly sure that this problem is new in 1:3.1.0-5 compared to
1:3.0.1-9 (I unfortunately didn't run the intermediate versions, so I
can't narrow it down further than that).
Let me know if there's any additional information I can provide.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages openoffice.org-common depends on:
ii openoffice.org-style-galaxy 1:3.1.0-5 full-featured office productivity
Versions of packages openoffice.org-common recommends:
ii openoffice.org-style-crystal 1:3.1.0-5 full-featured office productivity
ii openoffice.org-style-tango 1:3.1.0-5 full-featured office productivity
ii xfonts-mathml 2 Type1 Symbol font for MathML
Versions of packages openoffice.org-common suggests:
pn openoffice.org-style-hicontra <none> (no description available)
pn openoffice.org-style-industri <none> (no description available)
-- no debconf information
Reply to: