Version-Release number of selected component: youtube-dl-2014.04.11.1-1.fc20 Additional info: reporter: libreport-2.2.2 cmdline: python /usr/bin/youtube-dl https://www.youtube.com/watch?v=WN6iuUosBJg dso_list: python-libs-2.7.5-11.fc20.x86_64 executable: /usr/bin/youtube-dl kernel: 3.14.3-200.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: utils.py:984:write_string:IOError: [Errno 5] Input/output error Traceback (most recent call last): File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/usr/bin/youtube-dl/__main__.py", line 18, in <module> youtube_dl.main() File "/usr/bin/youtube-dl/youtube_dl/__init__.py", line 837, in main _real_main(argv) File "/usr/bin/youtube-dl/youtube_dl/__init__.py", line 827, in _real_main retcode = ydl.download(all_urls) File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1038, in download self.report_error('unable to download video') File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 404, in report_error self.trouble(error_message, tb) File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 357, in trouble self.to_stderr(message) File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 311, in to_stderr self._write_string(output, self._err_file) File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 290, in _write_string write_string(s, out=out, encoding=self.params.get('encoding')) File "/usr/bin/youtube-dl/youtube_dl/utils.py", line 984, in write_string out.write(byt) IOError: [Errno 5] Input/output error Local variables in innermost frame: byt: 'ERROR: unable to download video\n' out: <open file '<stderr>', mode 'w' at 0x7f718428a1e0> s: u'ERROR: unable to download video\n' encoding: None
Created attachment 896541 [details] File: backtrace
Created attachment 896542 [details] File: environ
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
seems to be fixed in current releases or it was a runtime error and then the error was probably fine.