supertuxkart crashed with SIGSEGV in irr::scene::CSkinnedMesh::recoverJointsFromMesh()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
supertuxkart (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I was just casually playing this game (again) when it happened.
I chose the track "Scotland" (but it also happened to other tracks).
In this version, 0.7.3, we have other characters and one of the newer ("Monkey") is not rendered properly.
I play this game on a machine with Ubuntu 12.04 LTS, in version 0.7.0 and this bahavior does not happen.
So, I guess, the Ubuntu 12.10 repository has a buggy version of this game.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: supertuxkart 0.7.3-2
ProcVersionSign
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Mon Oct 22 12:49:13 2012
ExecutablePath: /usr/games/
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
ProcCmdline: supertuxkart --log=file
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb7445e5d <_ZN3irr5scene1
PC (0xb7445e5d) ok
source "(%edi)" (0x6e6f6974) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: supertuxkart
StacktraceTop:
irr::scene:
irr::scene:
irr::scene:
irr::scene:
irr::scene:
Title: supertuxkart crashed with SIGSEGV in irr::scene:
UpgradeStatus: Upgraded to quantal on 2012-10-17 (4 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
XsessionErrors:
(gnome-
(gnome-
(geany:4329): LIBDBUSMENU-
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1047035, 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.