Description of problem: I've imported four videos into Pitivy library, draged one into the timeline at the bottom and then the crash occured. Version-Release number of selected component: pitivi-0.93-4.fc20 Additional info: reporter: libreport-2.2.2 cmdline: python2 /usr/bin/pitivi executable: /usr/bin/pitivi kernel: 3.14.3-200.fc20.x86_64 runlevel: N 5 type: Python uid: 500 Truncated backtrace: signal.py:187:emit:TypeError: _pipelineErrorCb() takes exactly 3 arguments (4 given) Traceback (most recent call last): File "/usr/share/pitivi/python/pitivi/utils/pipeline.py", line 458, in _busMessageCb self._handleErrorMessage(error, detail, message.src) File "/usr/share/pitivi/python/pitivi/utils/pipeline.py", line 496, in _handleErrorMessage self.emit('error', error.message, detail) File "/usr/share/pitivi/python/pitivi/utils/signal.py", line 212, in emit *args, **kwargs) File "/usr/share/pitivi/python/pitivi/utils/signal.py", line 187, in emit res = cb(*ar, **kw) TypeError: _pipelineErrorCb() takes exactly 3 arguments (4 given) Local variables in innermost frame: orar: () args: (<pitivi.utils.pipeline.AssetPipeline object at 0x4aeb550>, "Can't play a text file without video or visualizations.", 'gstplaysink.c(3003): gst_play_sink_do_reconfigure (): /GstPlayBin:preview-player/GstPlaySink:playsink:\nHave text pad but no video pad or visualizations') sigid: 10868721703048852882L signame: 'error' cb: <bound method PreviewWidget._pipelineErrorCb of <PreviewWidget object at 0x4aeacd0 (pitivi+mediafilespreviewer+PreviewWidget at 0x4bc7380)>> self: <pitivi.utils.signal.SignalGroup instance at 0x4aece18> kwargs: {} signame_handlers: [10868721703048852882L] ar: (<pitivi.utils.pipeline.AssetPipeline object at 0x4aeb550>, "Can't play a text file without video or visualizations.", 'gstplaysink.c(3003): gst_play_sink_do_reconfigure (): /GstPlayBin:preview-player/GstPlaySink:playsink:\nHave text pad but no video pad or visualizations') kw: {} res: None kwar: {}
Created attachment 901874 [details] File: backtrace
Created attachment 901875 [details] File: environ
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.