qgis.bin crashed with SIGSEGV in QVariantAnimation::keyValueAt()

[bp0]

I minimised the qgis window, then tried to re-maximise it, and it crashed. It may have something to do with python? I only suggest this as the later version of qgis (1.7 from oneiric) crashes when loading python.

Running Precise Beta 1 and QGIS 1.4.0+12730-5ubuntu2

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: qgis-plugin-grass 1.4.0+12730-5ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sun Mar 11 22:31:57 2012
ExecutablePath: /usr/bin/qgis.bin
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120308)
ProcCmdline: /usr/bin/qgis.bin
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6f72a26: mov 0x8(%esi),%eax
 PC (0xb6f72a26) ok
 source "0x8(%esi)" (0x732f3639) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: qgis
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QVariantAnimation::keyValueAt(double) const () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QVariantAnimation::startValue() const () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QPropertyAnimation::updateState(QAbstractAnimation::State, QAbstractAnimation::State) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
Title: qgis.bin crashed with SIGSEGV in QVariantAnimation::keyValueAt()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Brian Bloniarz (brianbloniarz)]

I'm seeing the same thing. My workaround for now is to use the newer version from the https://wiki.ubuntu.com/UbuntuGIS PPA.

[Bas Couwenberg (sebastic)]

Fixed since QGIS 2.0.1 in trusty at least.