Bug#534314: dies when started from mutt with "terminate called"
- To: Debian Bug Tracking System <email@example.com>
- Subject: Bug#534314: dies when started from mutt with "terminate called"
- From: Ferenc Wagner <firstname.lastname@example.org>
- Date: Tue, 30 Nov 2010 11:17:25 +0100
- Message-id: <email@example.com>
- Reply-to: Ferenc Wagner <firstname.lastname@example.org>, email@example.com
- In-reply-to: <20100107045337.GA18157@lapse.rw.madduck.net> (martin f. krafft's message of "Thu, 7 Jan 2010 17:53:37 +1300")
- References: <20100107045337.GA18157@lapse.rw.madduck.net>
martin f krafft <firstname.lastname@example.org> writes:
> Indeed, the bug seems to be caused by -no-oosplash, but it's to be
> looked for elsewhere:
> lapse:~|master|% /usr/lib/openoffice/program/soffice.bin
> terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException'
> If I call /usr/lib/openoffice/program/oosplash.bin instead, it works.
> Thus, I'd say that soffice.bin is simply screwed up.
This bug is still alive under current Squeeze, making OOo unusable from
external applications (Gnus, in my case). My arch is i386.
terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException'
On the other hand, it returns successfully if OOo is already running, for
example if it was started previously by
As I understand it, removing -no-oosplash from the mailcap entries opens
up a race, so it isn't a proper workaround. Or has it been working for
everybody else for almost a year now?