Bug#531750: openoffice.org: does not start
tag 531750 + moreinfo
tag 531750 + unreproducible
thanks
Roberto Lumbreras wrote:
> After upgrading the system, so ooffice has been upgraded from 2.4 to 3.0,
How did you upgrade? What did you upgrade? In what distro? Which packages
of OOo did you have installed *when the bug occured*? "Of course" your
bugreport doesn't mention anything of these. You as DD *really* should
know better....
(I'll now assume you did lenny->squeeze, architecture should not matter)
I just tried a lenny->squeeze dist-upgrade - with working package installation
*AND* working package afterwards, -> unreproducible.
Sigh. Another bogus report +moreinfo/+unreproducible. And that from a DD....
> $ openoffice.org
> /usr/lib/openoffice/program/soffice: line 213:
> /usr/lib/openoffice/program/../basis-link/program/pagein: No such file or
``````
> directory
> /usr/lib/openoffice/program/soffice.bin: error while loading shared
> libraries: libsofficeapp.so: cannot open shared object file: No such file
`````````````````
> or directory
> $ ldd /usr/lib/openoffice/program/soffice.bin
> linux-gate.so.1 => (0xb7f3d000)
> libuno_sal.so.3 => /usr/lib/libuno_sal.so.3 (0xb7d63000)
> libsofficeapp.so => not found
````````````````
> libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7c71000)
> libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7c45000)
> libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7ae5000)
> libpam.so.0 => /lib/libpam.so.0 (0xb7ada000)
> libcrypt.so.1 => /lib/i686/cmov/libcrypt.so.1 (0xb7aa8000)
> libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7aa3000)
> libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb7a8a000)
> libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7a64000)
> /lib/ld-linux.so.2 (0xb7f3e000)
This does not make sense. Those files are in -core. (And binaries needing
them *do* know where they are.)
And all modules have appropriate depends to pull in the -core/-common it needs
and conflicts to force older to be not installable with a newer OOo,
> Purging all openoffice packages and installing them again didn't solve the
> problem.
I bet your system is simply broken. Not every system breakage is a bug
in packages. It also might just be user error.
Grüße/Regards,
René
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' rene@debian.org | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
Reply to: