I hadn't used it for a month or so. Perhaps it got resentful.
Anyway, recent attempts to start any flavor of OpenOffice have failed
early.
It does ask about plugins, and whether it shour restore my session,
but shortly after that it simply dies. There's no dialog box,
and nothing obvious in the log files.
I've done revdep-rebuild, and its clean. Then I re-emerged
openoffice-bin (which is what I use). To no avail.
Any ideas?
--
Kevin O'Gorman, PhD
09-24-2008, 05:58 AM
Dale
Openoffice dies on startup
Kevin O'Gorman wrote:
I hadn't used it for a month or so. Perhaps it got resentful.
Anyway, recent attempts to start any flavor of OpenOffice have failed
early.
It does ask about plugins, and whether it shour restore my session,
but shortly after that it simply dies. There's no dialog box,
and nothing obvious in the log files.
I've done revdep-rebuild, and its clean. Then I re-emerged
openoffice-bin (which is what I use). To no avail.
Any ideas?
Have you upgraded python recently? I upgraded mine a while back and OOo
needed to recompile. You may want to run python-updater and check what
it says. It may be something else that OOo depends on that needs to
recompile. Not real sure since you use the binary version.
Hope that helps.
Dale
:-) :-)
09-24-2008, 07:22 AM
Iain Buchanan
Openoffice dies on startup
Kevin O'Gorman wrote:
I hadn't used it for a month or so. Perhaps it got resentful.
Anyway, recent attempts to start any flavor of OpenOffice have failed
early.
It does ask about plugins, and whether it shour restore my session,
but shortly after that it simply dies. There's no dialog box,
and nothing obvious in the log files.
I've done revdep-rebuild, and its clean. Then I re-emerged
openoffice-bin (which is what I use). To no avail.
Any ideas?
to see where it's dying, can you run:
$ gdb /usr/lib/openoffice/program/soffice.bin
and then when it dies in the gdb prompt:
(gdb) thread apply all bt
and post the output
This might not show much, if you use openoffice-bin, we'll see.
--
Iain Buchanan <iaindb at netspace dot net dot au>
[Peter gets fired]
Peter Griffin: Hey, Lois, the lost my job smells great. Hey, Meg, could
you pass me the fired my ass for negligence?
Lois Griffin: Peter, are you OK?
Peter Griffin: Great. I haven't got a job in the world.
09-24-2008, 07:33 AM
Dirk Heinrichs
Openoffice dies on startup
Am Mittwoch 24 September 2008 07:28:42 schrieb ext Kevin O'Gorman:
> I hadn't used it for a month or so. Perhaps it got resentful.
> Anyway, recent attempts to start any flavor of OpenOffice have failed
> early.
>
> It does ask about plugins, and whether it shour restore my session,
> but shortly after that it simply dies. There's no dialog box,
> and nothing obvious in the log files.
First thing I do in such cases is to start the thing from a shell, to see
what's printed on stderr/stdout. Most of the times this gives valuable hints.
> I've done revdep-rebuild, and its clean. Then I re-emerged
> openoffice-bin (which is what I use). To no avail.
>
> Any ideas?
emerge -C openoffice-bin && emerge openoffice
openoffice-bin has been compiled with a given set of use flags and on a
machine that may or may not match what you have. Compiling it yourself is
always the better idea.
On Wed, Sep 24, 2008 at 12:33 AM, Dirk Heinrichs
<dirk.heinrichs.ext@nsn.com> wrote:
> Am Mittwoch 24 September 2008 07:28:42 schrieb ext Kevin O'Gorman:
>> I hadn't used it for a month or so. Perhaps it got resentful.
>> Anyway, recent attempts to start any flavor of OpenOffice have failed
>> early.
>>
>> It does ask about plugins, and whether it shour restore my session,
>> but shortly after that it simply dies. There's no dialog box,
>> and nothing obvious in the log files.
>
> First thing I do in such cases is to start the thing from a shell, to see
> what's printed on stderr/stdout. Most of the times this gives valuable hints.
>
>> I've done revdep-rebuild, and its clean. Then I re-emerged
>> openoffice-bin (which is what I use). To no avail.
>>
>> Any ideas?
>
> emerge -C openoffice-bin && emerge openoffice
>
> openoffice-bin has been compiled with a given set of use flags and on a
> machine that may or may not match what you have. Compiling it yourself is
> always the better idea.
>
Not so obviously better when it fails. Here's the tail of what I get:
ERROR: Error 65280 occurred while making
/var/tmp/portage/app-office/openoffice-2.4.1/work/ooo/build/OOH680_m17/forms/util
make: *** [stamp/build] Error 1
*
* ERROR: app-office/openoffice-2.4.1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 5374: Called die
* The specific snippet of code:
* make || die "Build failed"
* The die message:
* Build failed
*
* If you need support, post the topmost build error, and the call
stack if relevant.
* A complete build log is located at
'/var/tmp/portage/app-office/openoffice-2.4.1/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/app-office/openoffice-2.4.1/temp/environment'.
*
!!! When you file a bug report, please include the following information:
GENTOO_VM=sun-jdk-1.6 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.6.0.07"
JAVACFLAGS="-source 1.4 -target 1.4" COMPILER=""
and of course, the output of emerge --info
* GNU info directory index is up-to-date.
treat ~ #
--
Kevin O'Gorman, PhD
09-25-2008, 03:56 AM
"Kevin O'Gorman"
Openoffice dies on startup
On Tue, Sep 23, 2008 at 10:58 PM, Dale <rdalek1967@gmail.com> wrote:
> Kevin O'Gorman wrote:
>>
>> I hadn't used it for a month or so. Perhaps it got resentful.
>> Anyway, recent attempts to start any flavor of OpenOffice have failed
>> early.
>>
>> It does ask about plugins, and whether it shour restore my session,
>> but shortly after that it simply dies. There's no dialog box,
>> and nothing obvious in the log files.
>>
>> I've done revdep-rebuild, and its clean. Then I re-emerged
>> openoffice-bin (which is what I use). To no avail.
>>
>> Any ideas?
>>
>>
>
> Have you upgraded python recently? I upgraded mine a while back and OOo
> needed to recompile. You may want to run python-updater and check what it
> says. It may be something else that OOo depends on that needs to recompile.
> Not real sure since you use the binary version.
>
> Hope that helps.
>
> Dale
>
You may be right. I tried to recompile OOo, and it pulled in 8 or so packages
that OOo-bin hadn't. Unfortunately, the compile eventually failed.
Am Donnerstag 25 September 2008 05:37:14 schrieb ext Kevin O'Gorman:
> > openoffice-bin has been compiled with a given set of use flags and on a
> > machine that may or may not match what you have. Compiling it yourself is
> > always the better idea.
>
> Not so obviously better when it fails. *Here's the tail of what I get:
You do have enough free space in the build directory (~6G)?
On Thu, Sep 25, 2008 at 2:08 AM, Dirk Heinrichs
<dirk.heinrichs.ext@nsn.com> wrote:
> Am Donnerstag 25 September 2008 05:37:14 schrieb ext Kevin O'Gorman:
>
>> > openoffice-bin has been compiled with a given set of use flags and on a
>> > machine that may or may not match what you have. Compiling it yourself is
>> > always the better idea.
>>
>> Not so obviously better when it fails. Here's the tail of what I get:
>
> You do have enough free space in the build directory (~6G)?
>
> Bye...
>
Apparently not. I just had something else fail, and I'm moving stuff around.
That's probably a major part of what's plagueing me now.
Openoffice dies on startup
