Seems like I've got version 2.3.7-1~getdeb1 installed now. I started all over again from mission 1 a few months ago and I played all the way to the last campaign without noticing the crash mentioned above. So I guess you can mark this one fixed. Sorry for not updating this bug (and thanks for reminding me!).
-- You received this bug notification because you are a member of Warzone 2100 Project, which is subscribed to warzone2100 in Ubuntu. https://bugs.launchpad.net/bugs/556912 Title: warzone2100 crashed with SIGSEGV in checkDroid() Status in “warzone2100” package in Ubuntu: Incomplete Bug description: Binary package hint: warzone2100 Might be a dup of 551335, but since I'm running 64 bit and it happened to me at the start of mission 10, I'm reporting this as a new bug. All I did was select a commander and try loading it into the transport. The game froze for a moment and then exited. ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: warzone2100 2.2.4-3 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Apr 7 00:21:11 2010 ExecutablePath: /usr/games/warzone2100 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcCmdline: warzone2100 ProcEnviron: LANGUAGE=en LANG=nl_NL.utf8 SHELL=/bin/bash Signal: 11 SourcePackage: warzone2100 StacktraceTop: checkDroid () electronicDroid () electronicDroid () electronicDroid () electronicDroid () Title: warzone2100 crashed with SIGSEGV in checkDroid() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (polkit-gnome-authentication-agent-1:1558): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed _______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev