anki crashed with SIGSEGV in QAbstractItemView::dataChanged()

Bug #511033 reported by Treibhauseffekt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
anki (Fedora)
Fix Released
Medium
anki (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: anki

Carried out update and opened program in parallel.

ProblemType: Crash
Architecture: i386
Date: Fri Jan 22 06:43:57 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/anki
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
Package: anki 0.9.9.7.8-1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/anki
ProcEnviron:
 LANGUAGE=de_AT.utf8
 LANG=de_AT.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
SegvAnalysis:
 Segfault happened at: 0x1cb5cdb: mov (%eax),%edx
 PC (0x01cb5cdb) ok
 source "(%eax)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: anki
StacktraceTop:
 ?? () from /usr/lib/libQtGui.so.4
 QAbstractItemView::dataChanged(QModelIndex const&, QModelIndex const&) () from /usr/lib/libQtGui.so.4
 ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtGui.so
 QAbstractItemView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtGui.so.4
 QTableView::qt_metacall(QMetaObject::Call, int, void**) ()
Title: anki crashed with SIGSEGV in QAbstractItemView::dataChanged()
Uname: Linux 2.6.32-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Treibhauseffekt (thomas-wuercher-hotmail-deactivatedaccount) wrote :
Revision history for this message
Damien Elmes (resolve) wrote :

this is a bug in pyqt 4.6.

Revision history for this message
Christian Krause (chkr) wrote :

Damien, in Fedora I can easily reproduce the problem even with PyQt4-4.7 and anki 0.9.8.8.5. Which exact update (qt4, PyQt4) triggered the problem I haven't figured out yet. I got feedback that an update to anki 0.9.8.8.6 actually solves this problem.

Revision history for this message
Andreas Moog (ampelbein) wrote :

The new version is in Ubuntu now.

Changed in anki (Ubuntu):
status: New → Fix Released
Changed in anki (Fedora):
importance: Unknown → Medium
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.