Bug 1282147

Summary: Pitivi isn't close to stable enough to be included in fedora
Product: [Fedora] Fedora Reporter: Rodd Clarkson <rodd>
Component: pitiviAssignee: Gwyn Ciesla <gwync>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: elad, gwync, hicham.haouari, nekohayo, otte, wtaymans
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-22 14:39:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rodd Clarkson 2015-11-15 04:49:44 UTC
Description of problem:

I can't get PiTiVi to run for more than about 1 minute (unless I open it and do nothing).

Importing clips crashes it some times

Trying to move tracks in the time line (which seems impossible, because there's no selection arrow crashes it sometimes.

Just opening it crashes it.

Video editing on Linux is hard enough without including packages that barely start.


Version-Release number of selected component (if applicable):

pitivi-0.94-5.fc23.x86_64


How reproducible:

Use if for about 1 minute.

Steps to Reproduce:
1. Open pitivi
2. Try to do something.
3.

Actual results:

Crashes very quickly


Expected results:

Some sort of stability would be appropriate before packages are included in fedora.


Additional info:

Comment 1 Jean-François Fortin Tam 2015-11-22 14:39:55 UTC
Crashes and such are to be reported upstream. Downstream, nobody hears your screams.

The Pitivi folks have been working for an entire year to stabilize the thing amidst all the breakage caused by $insert_dependencies_here (gst, clutter, gtk, wayland, you name it).

0.95 (bug #1283968) should be much better.

Comment 2 Jean-François Fortin Tam 2015-11-22 14:42:13 UTC
I should also mention that what ended up packaged downstream somehow behaved differently than upstream (bug #1178168).