Version-Release number of selected component: calibre-0.9.8-1.fc18 Additional info: cmdline: python2 /usr/bin/calibre-parallel executable: /usr/bin/calibre-parallel kernel: 3.6.10-4.fc18.x86_64 uid: 1000 Truncated backtrace: worker.py:92:do_read_metadata:IOError: [Errno 2] No such file or directory: u'/var/tmp/calibre_0.9.8_tmp_ZbPDp5/gWCx6p_rm_worker/0.error' Traceback (most recent call last): File "/usr/bin/calibre-parallel", line 20, in <module> sys.exit(main()) File "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 185, in main result = func(*args, **kwargs) File "/usr/lib64/calibre/calibre/ebooks/metadata/worker.py", line 42, in read_metadata_ do_read_metadata(task, tdir, mdir, notification) File "/usr/lib64/calibre/calibre/ebooks/metadata/worker.py", line 92, in do_read_metadata with open(os.path.join(tdir, '%s.error'%id_), 'wb') as f: IOError: [Errno 2] No such file or directory: u'/var/tmp/calibre_0.9.8_tmp_ZbPDp5/gWCx6p_rm_worker/0.error' Local variables in innermost frame: id_: 0 run_plugins_on_import: <functools.partial object at 0x1f598e8> formats: [u'/var/tmp/Linked_Data_v2_MEAP.epub'] name: u'Linked_Data_v2_MEAP' format: u'/var/tmp/Linked_Data_v2_MEAP.epub' notification: <Progress(Thread-1, started daemon 139746675861248)> traceback: <module 'traceback' from '/usr/lib64/python2.7/traceback.pyc'> fmts: [None] ext: u'.epub' task: [(0, [u'/var/tmp/Linked_Data_v2_MEAP.epub'])] tdir: u'/var/tmp/calibre_0.9.8_tmp_ZbPDp5/gWCx6p_rm_worker' mdir: u'/var/tmp/calibre_0.9.8_tmp_ZbPDp5/z4qx6p' nfp: None x: (0, [u'/var/tmp/Linked_Data_v2_MEAP.epub']) mfmt: u'/var/tmp/Linked_Data_v2_MEAP.epub' import_map: {} metadata_fmts: [u'/var/tmp/Linked_Data_v2_MEAP.epub']
Created attachment 677503 [details] File: backtrace
Created attachment 677505 [details] File: core_backtrace
Created attachment 677506 [details] File: environ
What were you doing when this happened? Can you duplicate it?
I'm not sure what's going on here. I'm in the process of rebuilding my laptop with Fedora 18 RC4 and the package repositories aren't responding sometimes. I think I started Calibre via Firefox - I downloaded a file and Firefox asked me what to use to open it and I picked Calibre. I can try to recreate it later; I'm switching from KDE to GNOME at the moment and I'll try it again when I get the system stabilized.
In the next few days there will be a newer calibre version available in updates-testing. Can you try: 'yum --enablerepo=updates-testing update calibre' and try and duplicate the problem with the new version? Thanks.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.