supertux crashed with SIGSEGV

[vashman]

Binary package hint: supertux-stable

Description: Ubuntu 9.10
Release: 9.10

supertux-stable
version: 0.1.3-1.1ubuntu3

1) Screen flashes to full screen then game closes and goes back to desktop. note:There is no sound though speaker do turn on.
2) Game worked before karmic, though was choppy and slow.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: e476e66e79edf85fd15eac94a6e4e0f9
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Fri Oct 30 13:21:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/games/supertux
Package: supertux-stable 0.1.3-1.1ubuntu3
ProcCmdline: supertux
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x53f000: lods %ds:(%esi),%eax
 PC (0x0053f000) ok
 source "%ds:(%esi)" (0xb251ce83) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: supertux-stable
StacktraceTop:
 ?? () from /usr/lib/libSDL-1.2.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: supertux crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2081): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2105): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2124): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (synaptic:2353): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #421946, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.