Public bug reported:

Binary package hint: openoffice.org

All mailcap entries calling openoffice contain: "soffice -no-oosplash"
>From a terminal, "soffice -no-oosplash" fails:
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'
But, "soffice -nologo" works perfectly!

After having a look at the script /usr/lib/openoffice/program/soffice, I tried 
some variants and got the following results:
calling soffice.bin or oosplash.bin from a terminal:
# /path/to/soffice.bin -nologo   --> works
# /path/to/soffice.bin -no-oosplash   --> crashes as described above
# /path/to/soffice.bin   --> crashes whith the same error !!!
# /path/to/oosplash.bin   --> works as proposed
# /path/to/oosplash.bin -nologo   --> starts without splash screen
# /path/to/oosplash.bin -no-oosplash   --> starts with splash screen !!!

As the shellscript soffice chooses one of the executables on the existence of 
the nologo or no-oosplash options, soffice.bin will normally never be called 
without one of these options. But it can't run without "-nologo", which I 
consider buggy at least.
The different behavior of oosplash.bin on the "-nologo" or "-no-oosplash" 
options makes me think that "-no-oosplash" shouldn't be used anymore.

So, all openoffice.org mailcap entries have to be changed from "soffice
-no-oosplash..."  to "soffice -nologo..." in order to call openoffice
programs via mailcap.  (In a second step, the viability of soffice.bin
without options should be addressed.)

My System Informations:
Ubuntu 9.10, all updates until current applied.
openoffice.org:
Installed: 1:3.1.1-5ubuntu1
Candidate: 1:3.1.1-5ubuntu1

** Affects: openoffice.org (Ubuntu)
     Importance: Undecided
         Status: New

-- 
soffice crashes when called from mutt (using mailcap entry)
https://bugs.launchpad.net/bugs/506399
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to