[Pkg-games-ubuntu] [Bug 454700] Re: unable to load any saved game

[Nick Moffitt]

Ansgar Burchardt:
> Nick Moffitt <nick at canonical.com> writes:
> > I just did a naïve backport with a bzr import-dsc on the karmic
> > version and then a merge-upstream from the .orig.tar.gz from debian
> > squeeze.  
> 
> Um, why didn't you just take the dsc from Debian and rebuild the
> package?  This way you would also get the remaining changes (e.g.
> updated translations).

I tried that first, but there were unmet build dependencies in my karmic
pbuilder.  Tossing on a new raw upstream tarball was the quickest route.
I'll try your PPA now, though.

-- 
Nick Moffitt

-- 
unable to load any saved game
https://bugs.launchpad.net/bugs/454700
You received this bug notification because you are a member of
Debian/Ubuntu Games Team, which is subscribed to simutrans in ubuntu.

Status in “simutrans” package in Ubuntu: Confirmed

Bug description:
Binary package hint: simutrans

Hi,

I've remarked that with Simutrans 102, there's no way to load a saved game.

How-to reproduce :
DO: start a game with Simutrans.
DO: save it.
DO: reload it.
EXPECTED BEHAVIOUR: game is loaded successfully.
ACTUAL BEHAVIOUR: an error occurs, message is :
"FATAL ERROR: planquadrat_t::rdwr()
Unknown ground type: -1".

Bug is reproducible with both games saved with version 102 of the game, and any previous revision.

ProblemType: Bug
Architecture: i386
Date: Sun Oct 18 16:10:58 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: simutrans 102.0-1
ProcEnviron:
 LANGUAGE=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: simutrans
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gpilotd:4704): gpilotd-WARNING **: Le nombre de périphériques est configuré à 0
 (gpilotd:4704): gpilotd-WARNING **: Aucun périphérique accessible disponible
 (gpilotd:4704): gpilotd-WARNING **: Le nombre de PDA est configuré à 0
 (polkit-gnome-authentication-agent-1:4723): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed