Bug 1394982

Summary: [abrt] pitivi: pipeline.py:451:_recover:pitivi.utils.pipeline.PipelineError: Should not try to recover after destroy
Product: [Fedora] Fedora Reporter: Neil <ledufff>
Component: pitiviAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: elad, gwync, otte, warmaximus, wtaymans
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/29143060495b413471bc3b76e824039caac3d201
Whiteboard: abrt_hash:72e2c9b35be188f1fe4fc45be632fe3c1a8c7705;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:16:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description Neil 2016-11-14 23:44:21 UTC
Version-Release number of selected component:
pitivi-0.97.1-2.fc24

Additional info:
reporter:       libreport-2.7.2
cmdline:        python3 /usr/bin/pitivi
executable:     /usr/bin/pitivi
kernel:         4.8.6-201.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           Python3
uid:            1001

Truncated backtrace:
pipeline.py:451:_recover:pitivi.utils.pipeline.PipelineError: Should not try to recover after destroy

Traceback (most recent call last):
  File "/usr/lib64/python3.5/site-packages/pitivi/utils/pipeline.py", line 297, in _asyncDoneNotReceivedCb
    self._recover()
  File "/usr/lib64/python3.5/site-packages/pitivi/utils/pipeline.py", line 451, in _recover
    raise PipelineError("Should not try to recover after destroy")
pitivi.utils.pipeline.PipelineError: Should not try to recover after destroy

Local variables in innermost frame:
self: <pipeline.AssetPipeline object at 0x7f64fd835f30 (pitivi+utils+pipeline+AssetPipeline at 0x561997675a80)>

Comment 1 Neil 2016-11-14 23:44:29 UTC
Created attachment 1220556 [details]
File: backtrace

Comment 2 Neil 2016-11-14 23:44:31 UTC
Created attachment 1220557 [details]
File: environ

Comment 3 Fedora End Of Life 2017-07-25 23:53:34 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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.

Comment 4 Fedora End Of Life 2017-08-08 19:16:20 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.