Bug#692070: wesnoth-1.10-core: does not start, wants libpython2.5.so.1.0

[Vincent Cheng]

Hi Harald,

On Thu, Nov 1, 2012 at 2:29 PM, Harald <bugreport at gehirnspen.de> wrote:
> Package: wesnoth-1.10-core
> Version: 1:1.10.4-1
> Severity: grave
> Justification: renders package unusable
>
> Good evening guys,
>
> I can't start wesnoth any more, it gives this output:
>
> ***
> oxi:|home/harald > wesnoth
> wesnoth: error while loading shared libraries: libpython2.5.so.1.0:
> cannot open shared object file: No such file or directory
> ***
>
> After I installed the python2.5 package, it finds the library, but again
> does not start. The output is:
>
> ***
> oxi:|home/harald > wesnoth
> wesnoth: error while loading shared libraries:
> libboost_iostreams-gcc42-mt-1_34_1.so.1.34.1: cannot open shared object
> file: No such file or directory
> ***
>
> I run an up-to-date "testing" system, wesnoth-1.10-core is the only
> "experimental" package. wesnoth-1.10-core and wesnoth-1.10-data are the
> only packages installed from the program. I experience the same problem
> with the 1.10.3 version in testing, and even compiled the game from
> sources (via apt). The same output.

Please uninstall your self-compiled wesnoth packages and/or
non-packaged binaries that you may have inadvertently installed; check
to make sure that you don't have any other wesnoth binaries sitting in
your $PATH ("whereis wesnoth" may help you out here). Then re-install
wesnoth-1.10-core and wesnoth-1.10-data and reply with the output of:
$ ldd /usr/games/wesnoth

> It is possible that this incident is connected to a complete update to
> actual "testing", first time for some months.

If you suspect that this bug was caused by an update, feel free to
attach your apt logs (look under /var/log/apt).

Regards,
Vincent