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 583041 - GStreamer error pops-up
GStreamer error pops-up
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: General
Git
Other All
: Normal normal
: 0.13.1
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-18 13:46 UTC by Stéphane Maniaci
Modified: 2009-05-20 08:52 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
debug log (658.67 KB, application/x-bzip)
2009-05-19 10:26 UTC, Stéphane Maniaci 		Details

Description Stéphane Maniaci 2009-05-18 13:46:35 UTC 
Please describe the problem:
When I add some elements (films) to my timeline, PiTiVi randomly pops-up an error.

Steps to reproduce:
1. Import multiple movie elements into timeline
2. Queue them one after one.
3. Get an error.


Actual results:
A popup displays with an error. But just click validate, and you can go on with your project.

Expected results:
Nothing :)

Does this happen every time?
No, actually it's kind of random, but it seems like it happens most of the time when you stick your element to the end of another element.

Other information:
Window title  : GStreamer a rencontré une erreur générale de flux. (GStreamer encountered a general stream error).

qtdemux.c(2408): gst_qtdemux_loop (): /GstPipeline:pipeline0/GstBin:bin0/GnlComposition:gnlcomposition1/GnlSource:gnlsource15/pitivi+elements+singledecodebin+SingleDecodeBin:pitivi+elements+singledecodebin+singledecodebin20/GstQTDemux:qtdemux94:
streaming stopped, reason not-linked
Comment 1 Edward Hervey 2009-05-18 16:55:20 UTC 
I've tried (in vain) to reproduce that issue with debugging.

Could you try to reproduce the issue with the following:

GST_DEBUG=3,qtdemux:5 PITIVI_DEBUG=5 pitivi > log 2>&1

And then compress the log (bzip2 log) and attach it to this bug report.
Comment 2 Stéphane Maniaci 2009-05-19 10:26:31 UTC 
Created attachment 134923 [details]
debug log
Comment 3 Edward Hervey 2009-05-20 08:52:39 UTC 
Confirmed as fixed on IRC