pitivi crashed with SIGSEGV in PyEval_EvalCodeEx()

Bug #646244 reported by Ernst Eeldert on 2010-09-23
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pitivi (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: pitivi

I just dragged about 15 clips to the timeline. I did not do any timeline scale changes at the same time, as reported in the other bug.

The behavior is consistent, ie. after I restart pitivi, it does the same thing.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: pitivi 0.13.5-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic-pae 2.6.35.4
Uname: Linux 2.6.35-20-generic-pae i686
Architecture: i386
CrashCounter: 1
Date: Thu Sep 23 20:50:17 2010
ExecutablePath: /usr/bin/pitivi
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: python /usr/bin/pitivi
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80df43a <PyEval_EvalCodeEx+218>: addl $0x1,(%edx)
 PC (0x080df43a) ok
 source "$0x1" ok
 destination "(%edx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: pitivi
StacktraceTop:
 PyEval_EvalCodeEx ()
 ?? ()
 PyObject_Call ()
 ?? ()
 PyObject_Call ()
Title: pitivi crashed with SIGSEGV in PyEval_EvalCodeEx()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

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 #642426, 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers