After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 622436 - Pitivi fails to open
Pitivi fails to open
Status: RESOLVED DUPLICATE of bug 583909
Product: pitivi
Classification: Other
Component: User interface
0.13.4
Other Linux
: Normal critical
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-22 20:24 UTC by David Wood
Modified: 2010-06-23 07:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Wood 2010-06-22 20:24:40 UTC
Binary package hint: pitivi

Pitivi fails to open when run, no errors are displayed when run from the menu, but running "pitivi" on the terminal reports the following:

(pitivi:5375): GStreamer-CRITICAL **:
Trying to dispose object "ffmpegcsp0", but it still has a parent "pitivi+elements+mixer+smartvideomixerbin0".
You need to let the parent manage the object instead of unreffing the object directly.

(pitivi:5375): GStreamer-CRITICAL **:
Trying to dispose object "src", but it still has a parent "pitivi+elements+mixer+smartvideomixerbin0".
You need to let the parent manage the object instead of unreffing the object directly.

Segmentation fault

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: pitivi 0.13.4-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-4.5-generic 2.6.35-rc3
Uname: Linux 2.6.35-4-generic x86_64
Architecture: amd64
Date: Tue Jun 22 21:05:21 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100602.2)
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: pitivi
Comment 1 Fabio Durán Verdugo 2010-06-22 21:50:55 UTC
today update gstreamer for ubuntu maverick and this bug I can't reproduce.

can you update and comment for this reports?
Comment 2 Edward Hervey 2010-06-23 07:01:32 UTC
This was a pygobject bug which is now fixed

*** This bug has been marked as a duplicate of bug 583909 ***