Bug 708577 - [abrt] pitivi-0.13.5-5.fc15: pipeline.py:269:setState:PipelineError: Failure changing state of the gst.Pipeline to <enum GST_STATE_PAUSED of type GstState>, currently reset to NULL
Summary: [abrt] pitivi-0.13.5-5.fc15: pipeline.py:269:setState:PipelineError: Failure ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pitivi
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:34b4caf475d460766424a67378e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-28 06:24 UTC by kxra
Modified: 2011-06-24 03:58 UTC (History)
3 users (show)

Fixed In Version: pitivi-0.14.0-2.fc15
Clone Of:
Environment:
Last Closed: 2011-06-24 03:58:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description kxra 2011-05-28 06:24:44 UTC
abrt version: 2.0.1
architecture:   x86_64
cmdline:        python /usr/bin/pitivi test.xptv
component:      pitivi
executable:     /usr/bin/pitivi
kernel:         2.6.38.6-26.rc1.fc15.x86_64
os_release:     Fedora release 15 (Lovelock)
package:        pitivi-0.13.5-5.fc15
reason:         pipeline.py:269:setState:PipelineError: Failure changing state of the gst.Pipeline to <enum GST_STATE_PAUSED of type GstState>, currently reset to NULL
time:           Fri May 27 22:51:07 2011
uid:            500
username:       danny

backtrace:
:pipeline.py:269:setState:PipelineError: Failure changing state of the gst.Pipeline to <enum GST_STATE_PAUSED of type GstState>, currently reset to NULL
:
:Traceback (most recent call last):
:  File "/usr/share/pitivi/python/pitivi/ui/mainwindow.py", line 244, in _recordCb
:    self.showEncodingDialog(self.project)
:  File "/usr/share/pitivi/python/pitivi/ui/mainwindow.py", line 234, in showEncodingDialog
:    project.pipeline.pause()
:  File "/usr/share/pitivi/python/pitivi/pipeline.py", line 295, in pause
:    self.setState(STATE_PAUSED)
:  File "/usr/share/pitivi/python/pitivi/pipeline.py", line 269, in setState
:    raise PipelineError("Failure changing state of the gst.Pipeline to %r, currently reset to NULL" % state)
:PipelineError: Failure changing state of the gst.Pipeline to <enum GST_STATE_PAUSED of type GstState>, currently reset to NULL
:
:Local variables in innermost frame:
:res: <enum GST_STATE_CHANGE_FAILURE of type GstStateChangeReturn>
:state: <enum GST_STATE_PAUSED of type GstState>
:self: <pitivi.pipeline.Pipeline object at 0x277af90>

Comment 1 Fedora Update System 2011-06-05 18:00:10 UTC
pitivi-0.14.0-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/pitivi-0.14.0-1.fc15

Comment 2 Fedora Update System 2011-06-07 04:43:51 UTC
Package pitivi-0.14.0-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pitivi-0.14.0-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/pitivi-0.14.0-1.fc15
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2011-06-14 17:29:51 UTC
pitivi-0.14.0-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/pitivi-0.14.0-2.fc15

Comment 4 Fedora Admin XMLRPC Client 2011-06-20 20:54:50 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora Admin XMLRPC Client 2011-06-20 20:56:42 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora Admin XMLRPC Client 2011-06-20 21:04:18 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Fedora Update System 2011-06-24 03:58:13 UTC
pitivi-0.14.0-2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.