GNOME Bugzilla – Bug 633532
pitivi crashed with SIGSEGV
Last modified: 2011-01-23 14:37:48 UTC
Binary package hint: pitivi Crash when moving an imported video (flv) to the timeline. ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: pitivi 0.13.5-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: fglrx wl Architecture: i386 Date: Mon Oct 25 17:15:12 2010 ExecutablePath: /usr/bin/pitivi InterpreterPath: /usr/bin/python2.6 PackageArchitecture: all ProcCmdline: python /usr/bin/pitivi ProcCwd: /home/linus ProcEnviron: LANG=de_DE.utf8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x9ddb576: mov 0x10(%eax),%edi PC (0x09ddb576) ok source "0x10(%eax)" (0x00000010) not located in a known VMA region (needed readable region)! destination "%edi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: pitivi StacktraceTop: ?? () from /usr/lib/gstreamer-0.10/libgstflv.so ?? () from /usr/lib/gstreamer-0.10/libgstflv.so ?? () from /usr/lib/gstreamer-0.10/libgstflv.so ?? () from /usr/lib/libgstreamer-0.10.so.0 ?? () from /usr/lib/libgstreamer-0.10.so.0 Title: pitivi crashed with SIGSEGV UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers reported on Launchpad, for details (Trace) see https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/666352
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? In your case, make sure you have the following packages installed: python-dbg python-gtk2-dbg python-gst0.10-dbg gstreamer0.10-gnonlin-dbg *gstreamer0.10*-dbg libglib2.0-0-dbg python-cairo-dbg See also http://live.gnome.org/GettingTraces for more information. You could also provide the video so I can test if I can reproduce the problem. Thanks in advance!
As indicated downstream, probable duplicate of bug #632260
(In reply to comment #2) > As indicated downstream, probable duplicate of bug #632260 for me is the same bug. could mark with dup?.
*** This bug has been marked as a duplicate of bug 632260 ***