[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#582160: [Rene Engelhard] Re: Bug#582160: openoffice.org-common: Crashes on a particular file



(Somehow this message reached me, but not the bug log in Cc)

--- Begin Message ---
On Wed, May 26, 2010 at 11:31:00PM +0200, Frank Küster wrote:
> Hm, maybe crash is the wrong word.  What happens is that Openoffice
> restarts itself and tries to recover the files it had open before I
> called it with the problematic file. That means, if it isn't running and
> I call 
[...]

That is a crash :)

> script. What it runs is
> 
> /usr/lib/openoffice/program/oosplash.bin Briefbogen_adfc_de_oo_neu_farbe.odt

No, it doesn't. It runs soffice.bin.

>From soffice:
[...]
sd_binary=`basename "$0"`.bin
[...]
# execute soffice binary
"$sd_prog/$sd_binary" "$@" &

-> soffice.bin.

That before that the splash is executed does not matter.

> But it's not so simple that something isn't accessible/executable that should be:

Why is it so hard to just run the real office binary? You dodn't and just
ran the splash screen. Nothing else.

> > Can you also send a gdb bt please?
> 
> Sorry, what do I need to do?  I don't know what "bt" means.  I have
> openoffice.org-dbg installed, but this is what I get:
> 
> $ gdb /usr/lib/openoffice/program/oosplash.bin 

So far OK, escept with soffice.bin, of course.

> Program exited normally.

Of course. The splash screen doesn't crash.

If you did it right and it crahses and you get to that (gdb) prompt,
run "bt".
(And btw, you of course want to use run Briefbogen_adfc_de_oo_neu_farbe.odt"
if you want that opened during the start)

Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  rene@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70


--- End Message ---

-- 
Dr. Frank Küster
Debian Developer (TeXLive)
VCD Aschaffenburg-Miltenberg, ADFC Miltenberg
B90/Grüne KV Miltenberg

Reply to: