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 583226 - can't render, clowns will eat me
can't render, clowns will eat me
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: General
Git
Other Linux
: Normal blocker
: 0.13.2
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on: 585794
Blocks:
 
 
Reported: 2009-05-19 16:43 UTC by Jean-François Fortin Tam
Modified: 2009-07-24 15:38 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
debug log (93.83 KB, application/x-gzip)
2009-05-19 16:43 UTC, Jean-François Fortin Tam 		Details

Description Jean-François Fortin Tam 2009-05-19 16:43:04 UTC 
I get this traceback:

Traceback (most recent call last):

+ Trace 215604

  • File "pitivi/ui/encodingdialog.py", line 130 in _recordButtonClickedCb 
    self.addRecordAction()
  • File "pitivi/ui/encodingdialog.py", line 182 in addRecordAction 
    self.renderaction.activate()
  • File "pitivi/action.py", line 119 in activate 
    self._ensurePipelineObjects()
  • File "pitivi/action.py", line 587 in _ensurePipelineObjects 
    self._activateLink(*link)
  • File "pitivi/action.py", line 599 in _activateLink 
    self.pipeline.getBinForFactoryStream(producer, prodstream)
  • File "pitivi/pipeline.py", line 492 in getBinForFactoryStream 
    stream, automake)
  • File "pitivi/pipeline.py", line 455 in _getStreamEntryForFactoryStream 
    raise PipelineError() pitivi.pipeline.PipelineError


Will attach a debug log.
Comment 1 Jean-François Fortin Tam 2009-05-19 16:43:48 UTC 
Created attachment 134958 [details]
debug log

For great justice.
Comment 2 Edward Hervey 2009-05-20 16:25:14 UTC 
coul you give us more details of when it happened ? And which revision ?
Comment 3 Jean-François Fortin Tam 2009-05-21 00:35:37 UTC 
This bug followed bug #583147 ; right after it was fixed, I went to test and hit the present error. As such, I don't know exactly when this started happening (if this wasn't here from the start somehow). I guess if I look at 583147, this must have started happening when formatter gained the ability to remember project settings and render/codec settings...
Comment 4 Edward Hervey 2009-06-14 09:09:42 UTC 
Jeff, is this still an issue with current git ?
Comment 5 Jean-François Fortin Tam 2009-06-15 22:58:59 UTC 
Nope, it's gone now.