warzone2100 crashed with SIGSEGV in checkDroid()

[iGadget]

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

[Apport retracing service (apport)]

StacktraceTop:
 checkDroid (droid=0x3abfb50,
 electronicDroid (psDroid=0x3abfb50) at droid.c:4103
 electronicDroid (psDroid=<value optimized out>)
 electronicDroid (psDroid=<value optimized out>)
 electronicDroid (psDroid=<value optimized out>)

[Paul Wise (Debian) (pabs)]

I just uploaded 2.3.2 to Debian sid, please test it when it reaches Ubuntu.

[Paul Wise (Debian) (pabs)]

2.3.4 is available, please test.

[Timmy Shih Jun Yee (shijun)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[iGadget (igadget)]

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!).

[Timmy Shih Jun Yee (shijun)]

Thank you for your reply.