pitivi crashed with PipelineError in setState(): Failure changing state of the gst.Pipeline to <enum GST_STATE_PAUSED of type GstState>, currently reset to NULL

[Lars Falk-Petersen]

Binary package hint: pitivi

Crash while importing vob files.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: pitivi 0.13.5-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CheckboxSubmission: 5401beee4df9de1328bc3bd499ef8963
CheckboxSystem: 6ad150425aaa21ef4b8052dede68bfca
Date: Wed Apr 13 16:33:42 2011
ExecutablePath: /usr/bin/pitivi
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/pitivi
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/pitivi']
SourcePackage: pitivi
Title: pitivi crashed with PipelineError in setState(): Failure changing state of the gst.Pipeline to <enum GST_STATE_PAUSED of type GstState>, currently reset to NULL
UpgradeStatus: Upgraded to natty on 2011-03-25 (19 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Lars Falk-Petersen (julenissen)]

Happened at same time as https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/759859

[Jeff Fortin Tam (kiddo)]

Thanks for taking the time to report this bug.
Without bug reproduction instructions (and ideally, debug logs) it's very hard to determine what caused it.

Does it happen only with specific video files? If so, providing samples of such files may be helpful.

Please provide precise steps to trigger the bug.
You can also create debug logs by running pitivi like this:
PITIVI_DEBUG=*:5 GST_DEBUG=2 /usr/bin/pitivi > debug.log 2>&1

Then compress and attach the log file to this bug report.

[Nawaf Alsallami (nawaf)]

It didn't occur again. I'll post debug data if it crashed again. Thanks.

[Jeff Fortin Tam (kiddo)]

I've finally managed to encounter the same error with a particular test case. See https://bugzilla.gnome.org/show_bug.cgi?id=652923 for details. However, I'm not sure it is the exact same issue.