Bug 1400483

Summary: [abrt] pitivi: application.py:267:_setScenarioFile:OSError: [Errno 5] Input/output error
Product: [Fedora] Fedora Reporter: vivek.hyperspace
Component: pitiviAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: elad, gwync, otte, wtaymans
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:9926cd817409c1a9b798be09cc0bd03c17d58415;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:06:15 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 vivek.hyperspace 2016-12-01 10:48:27 UTC
Version-Release number of selected component:
pitivi-0.97.1-3.fc25

Additional info:
reporter:       libreport-2.8.0
cmdline:        python3 /usr/bin/pitivi /run/media/vivek/NEW/VIDEO_TS/VTS_01_1.VOB
executable:     /usr/bin/pitivi
kernel:         4.8.10-300.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
application.py:267:_setScenarioFile:OSError: [Errno 5] Input/output error

Traceback (most recent call last):
  File "/usr/lib64/python3.5/site-packages/pitivi/application.py", line 272, in _newProjectLoadingCb
    self._setScenarioFile(project.get_uri())
  File "/usr/lib64/python3.5/site-packages/pitivi/application.py", line 267, in _setScenarioFile
    content = project.read().replace("\n", "")
OSError: [Errno 5] Input/output error

Local variables in innermost frame:
self: <application.Pitivi object at 0x7f833fa47d80 (pitivi+application+Pitivi at 0x55a3ee740270)>
uri: 'file:///run/media/vivek/NEW/VIDEO_TS/VTS_01_1.VOB'
cache_dir: '/home/vivek/.cache/pitivi/scenarios'
scenario_path: '/home/vivek/.cache/pitivi/scenarios/20161201-094036_run_media_vivek_NEW_VIDEO_TS_VTS_01_1.scenario'
scenario_name: '20161201-094036_run_media_vivek_NEW_VIDEO_TS_VTS_01_1'
project: <_io.TextIOWrapper name='/run/media/vivek/NEW/VIDEO_TS/VTS_01_1.VOB' mode='r' encoding='UTF-8'>
project_path: '/run/media/vivek/NEW/VIDEO_TS/VTS_01_1.VOB'

Comment 1 vivek.hyperspace 2016-12-01 10:48:31 UTC
Created attachment 1226734 [details]
File: backtrace

Comment 2 vivek.hyperspace 2016-12-01 10:48:33 UTC
Created attachment 1226735 [details]
File: environ

Comment 3 Fedora End Of Life 2017-11-16 15:15:04 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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-12-12 10:06:15 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.